Methods and apparatus for power-efficient positioning in wireless communication systems

ABSTRACT

Method, apparatus, and systems for determining and transmitting positioning information in a wireless communication network are provided. For example, a method for wireless communications comprises receiving configuration information related to a set of positioning configurations and a small data transmission (SDT), determining, based on the configuration information, that at least one positioning configuration of the set of positioning configurations satisfies a positioning requirement and is associated with a payload size being less than a data volume threshold (DVT) associated with the SDT, selecting, from the at least one positioning configuration, positioning configuration associated with a payload size being closest to the DVT, performing a positioning measurement based on the selected positioning configuration, and sending, using an uplink resource for the SDT, a measurement report based on the selected positioning configuration and the positioning measurement.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to and the benefit of U.S. ProvisionalApplication No. 63/091,399 filed in the U.S. Patent and Trademark Officeon Oct. 14, 2020, U.S. Provisional Application No. 63/134,331 filed inthe U.S. Patent and Trademark Office on Jan. 6, 2021, U.S. ProvisionalApplication No. 63/167,985 filed in the U.S. Patent and Trademark Officeon Mar. 30, 2021, and U.S. Provisional Application No. 63/227,496 filedin the U.S. Patent and Trademark Office on Jul. 30, 2021, the entirecontents of each of which being incorporated herein by reference as iffully set forth below in their entirety and for all applicable purposes.

BACKGROUND

In the 3rd Generation Partnership Project (3GPP) standards (e.g., 3GPPRelease 16), downlink, uplink, and downlink and uplink positioningmethods are specified.

In the downlink positioning method(s), Positioning Reference Signals(PRSs) are sent from multiple Transmission/Reception Points (TRPs) of awireless communication network to a WTRU. The WTRU will observe multiplereference signals and measure time difference of arrival between a pairof PRSs. Then, the WTRU returns measured Reference Signal TimeDifference (RSTD) to the Location Management Function (LMF). Inaddition, the WTRU can return measured Reference Signal Received Power(RSRP) for each PRS. Based on the returned measurements, the LMFconducts positioning of the WTRU. Alternatively, the WTRU can reportRSRP for downlink (DL) angle-based positioning methods.

In the uplink positioning method(s), the WTRU sends a Sounding ReferenceSignal (SRS) for positioning, configured by Radio Resource Control (RRC)signaling, to Reception Points (RPs) or TRPs. For timing-based methods,TRP measures Relative Time of Arrival (RTOA) for received SRS signalsand reports measured values to the LMF. The WTRU can report RSRP forSRS. In angle-based uplink positioning methods, an RP or TRP willmeasure angles of arrival and report it to the LMF.

In the uplink and downlink positioning method(s), a WTRU measures Rx-Txtime difference between a received PRS and a transmitted SRS. The Rx-Txtime difference is reported to the LMF. The WTRU can also reportmeasured RSRP for PRS and, the TRP computes the Rx-Tx difference betweenthe received SRS and the transmitted PRS.

A “DL positioning method” may refer to any positioning method thatrequires downlink reference signals, such as PRS. In such positioningtechniques, the WTRU may receive multiple reference signals from TP andmeasures DL RSTD and/or RSRP. Examples of DL positioning methods includeDL-AoD or DL-TDOA positioning.

A “UL positioning method” may refer to any positioning technique thatrequires uplink reference signals, such as SRS for positioning. In suchtechniques, the WTRU may transmit SRS to multiple RPs or TRPs, and theRPs or TRPs measure the UL RTOA and/or RSRP. Examples of UL positioningmethods include UL-TDOA or UL-AoA positioning.

A “DL and UL positioning method” may refer to any positioning methodthat requires both uplink and downlink reference signals forpositioning. In one example, a WTRU transmits SRS to multiple TRPs and agNB measures the Rx-Tx time difference. The gNB can measure RSRP for thereceived SRS. The WTRU measures Rx-Tx time difference for PRSstransmitted from multiple TRPs. The WTRU can measure RSRP for thereceived PRS. The Rx-TX difference, and possibly RSRP measured at theWTRU and the gNB, are used to compute round trip time. Here, Rx and Txdifference refers to the difference between arrival time of thereference signal transmitted by the TRP and transmission time of thereference signal transmitted from the WTRU. An example of DL and ULpositioning method is multi-Round Trip Time (RTT) positioning.

A DL-based positioning (and possibly DL and UL positioning) is eitherWTRU-based (i.e., the WTRU conducts positioning) or WTRU-assisted (thenetwork conducts the positioning operations using with measurementreports sent from the WTRU).

In various embodiments, the term “network” is inclusive of AMF, LMF,and/or NG-RAN.

SUMMARY

Embodiments disclosed herein generally relate to wireless communicationnetworks. For example, one or more embodiments disclosed herein arerelated to method, apparatus, and systems for determining andtransmitting positioning information (e.g., a geographic position,positioning configurations, positioning measurements, and/or ameasurement report for positioning) in a wireless communication network.Various embodiments and methods may be implemented in a wirelesstransmit/receive unit (WTRU) in a wireless communication network (e.g.,a cellular network), while in a low-power state, such as a low-powerconnectivity state, an Idle state, and/or an inactive state.

In one embodiment, a method implemented in a WTRU for wirelesscommunications includes receiving configuration information related to aset of positioning configurations and a small data transmission (SDT),determining, based on the configuration information, that at least onepositioning configuration of the set of positioning configurationssatisfies a positioning requirement and is associated with a payloadsize being less than a data volume threshold (DVT) associated with theSDT, selecting, from the at least one positioning configuration, apositioning configuration associated with a payload size being closestto the DVT, performing a positioning measurement based on the selectedpositioning configuration, and sending, using an uplink resource for theSDT, a measurement report based on the selected positioningconfiguration and the positioning measurement.

In one embodiment, a method implemented in a WTRU for wirelesscommunications includes receiving assistance data including one or morePositioning Reference Signal (PRS) configurations, each PRSconfiguration may include a measurement configuration and/or ameasurement report configuration. At least one of the PRS configurationsmay be indicated to meet a minimum accuracy requirement. The method mayalso include sending an indication (e.g., to a gNB) of the payload sizes(of measurement report(s)) associated with the one or more PRSconfigurations. The method may include receiving a small datatransmission (SDT) configuration (e.g., from the gNB) including a datavolume threshold (DVT) for SDT (e.g., indicating the maximum payloadsize for SDT). On condition that at least one PRS config from the one ormore received PRS configurations indicated to satisfy the minimumaccuracy requirement has an associated payload size less than the DVTfor SDT, the method may include selecting a PRS config with anassociated payload size closest to the DVT for SDT from among the atleast one PRS configurations that satisfy the minimum accuracyrequirement; and performing PRS measurements and sending a measurementreport (to the LMF) based on the selected PRS config using an SDT (e.g.,in an INACTIVE state), and the measurement report indicates the selectedPRS config and the DVT for SDT. On condition that none of the PRSconfigurations indicated to satisfy the minimum accuracy requirementhave an associated payload size less than the DVT for SDT, the methodmay include sending a connection request (e.g., to the gNB to transitionto a CONNECTED state to be able to send a measurement report).

BRIEF DESCRIPTION OF THE DRAWINGS

A more detailed understanding may be had from the detailed descriptionbelow, given by way of example in conjunction with the drawings appendedhereto. Figures in such drawings, like the detailed description, areexemplary. As such, the Figures and the detailed description are not tobe considered limiting, and other equally effective examples arepossible and likely. Furthermore, like reference numerals (“ref.”) inthe Figures (“FIGs.”) indicate like elements, and wherein:

FIG. 1A is a system diagram illustrating an example communicationssystem in which one or more disclosed embodiments may be implemented;

FIG. 1B is a system diagram illustrating an example wirelesstransmit/receive unit (WTRU) that may be used within the communicationssystem illustrated in FIG. 1A according to an embodiment;

FIG. 1C is a system diagram illustrating an example radio access network(RAN) and an example core network (CN) that may be used within thecommunications system illustrated in FIG. 1A according to an embodiment;

FIG. 1D is a system diagram illustrating a further example RAN and afurther example CN that may be used within the communications systemillustrated in FIG. 1A according to an embodiment;

FIG. 2 is a signaling flow chart for 4-step RACH for DL positioningmethods for measurement report transmission during inactive mode inaccordance with an embodiment;

FIG. 3 is a signaling flow chart for 2-step RACH for DL positioningmethods for measurement report transmission during inactive mode inaccordance with an embodiment;

FIG. 4 is a signaling flow chart for 2-step RACH for UL positioningmethods for measurement report transmission during inactive mode inaccordance with an embodiment;

FIG. 5 is a signaling flow chart for 2-step RACH for UL positioningmethods for measurement report transmission during inactive mode inaccordance with an embodiment;

FIG. 6 is a signaling flow chart for positioning during WTRU Inactivemode mobility illustrating PRS configuration and RNA alignment inaccordance with an embodiment;

FIG. 7 is a signaling flow chart for positioning during WTRU Inactivemode mobility illustrating SRS configuration and RNA alignment inaccordance with an embodiment;

FIG. 8 is a signaling flow chart for positioning during WTRU idle modemobility illustrating PRS configuration and Tracking Area alignment inaccordance with an embodiment;

FIG. 9 is a signaling flow chart for positioning during WTRUIdle/Inactive mode with PRS configuration and DRX cycle alignment inaccordance with an embodiment;

FIG. 10 is a signaling flow chart for positioning during WTRU Inactivemode mobility for SRS configuration and RNA alignment in accordance withan embodiment;

FIG. 11 is a signaling flow chart for positioning during WTRU Inactivemode mobility for trigger-based update for SRS configuration and RNAalignment in accordance with an embodiment;

FIG. 12 is a flowchart illustrating a procedure for measurementreporting in accordance with an embodiment; and

FIG. 13 is a diagram illustrating positioning measurements and reportingin INACTIVE vs. CONNECTED state based on a positioning requirement(e.g., accuracy requirements) and a data volume threshold for SDT.

DETAILED DESCRIPTION Introduction

In the following detailed description, numerous specific details are setforth to provide a thorough understanding of embodiments and/or examplesdisclosed herein. However, it will be understood that such embodimentsand examples may be practiced without some or all of the specificdetails set forth herein. In other instances, well-known methods,procedures, components and circuits have not been described in detail,so as not to obscure the following description. Further, embodiments andexamples not specifically described herein may be practiced in lieu of,or in combination with, the embodiments and other examples described,disclosed or otherwise provided explicitly, implicitly and/or inherently(collectively “provided”) herein. Although various embodiments aredescribed and/or claimed herein in which an apparatus, system, device,etc. and/or any element thereof carries out an operation, process,algorithm, function, etc. and/or any portion thereof, it is to beunderstood that any embodiments described and/or claimed herein assumethat any apparatus, system, device, etc. and/or any element thereof isconfigured to carry out any operation, process, algorithm, function,etc. and/or any portion thereof.

FIG. 1A is a diagram illustrating an example communications system 100in which one or more disclosed embodiments may be implemented. Thecommunications system 100 may be a multiple access system that providescontent, such as voice, data, video, messaging, broadcast, etc., tomultiple wireless users. The communications system 100 may enablemultiple wireless users to access such content through the sharing ofsystem resources, including wireless bandwidth. For example, thecommunications systems 100 may employ one or more channel accessmethods, such as code division multiple access (CDMA), time divisionmultiple access (TDMA), frequency division multiple access (FDMA),orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tailunique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM(UW-OFDM), resource block-filtered OFDM, filter bank multicarrier(FBMC), and the like.

As shown in FIG. 1A, the communications system 100 may include wirelesstransmit/receive units (WTRUs) 102 a, 102 b, 102 c, 102 d, a RAN104/113, a CN 106/115, a public switched telephone network (PSTN) 108,the Internet 110, and other networks 112, though it will be appreciatedthat the disclosed embodiments contemplate any number of WTRUs, basestations, networks, and/or network elements. Each of the WTRUs 102 a,102 b, 102 c, 102 d may be any type of device configured to operateand/or communicate in a wireless environment. By way of example, theWTRUs 102 a, 102 b, 102 c, 102 d, any of which may be referred to as a“station” and/or a “STA”, may be configured to transmit and/or receivewireless signals and may include a user equipment (UE), a mobilestation, a fixed or mobile subscriber unit, a subscription-based unit, apager, a cellular telephone, a personal digital assistant (PDA), asmartphone, a laptop, a netbook, a personal computer, a wireless sensor,a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watchor other wearable, a head-mounted display (HMD), a vehicle, a drone, amedical device and applications (e.g., remote surgery), an industrialdevice and applications (e.g., a robot and/or other wireless devicesoperating in an industrial and/or an automated processing chaincontexts), a consumer electronics device, a device operating oncommercial and/or industrial wireless networks, and the like. Any of theWTRUs 102 a, 102 b, 102 c and 102 d may be interchangeably referred toas a UE.

The communications systems 100 may also include a base station 114 aand/or a base station 114 b. Each of the base stations 114 a, 114 b maybe any type of device configured to wirelessly interface with at leastone of the WTRUs 102 a, 102 b, 102 c, 102 d to facilitate access to oneor more communication networks, such as the CN 106/115, the Internet110, and/or the other networks 112. By way of example, the base stations114 a, 114 b may be a base transceiver station (BTS), a Node-B, an eNodeB, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller,an access point (AP), a wireless router, and the like. While the basestations 114 a, 114 b are each depicted as a single element, it will beappreciated that the base stations 114 a, 114 b may include any numberof interconnected base stations and/or network elements.

The base station 114 a may be part of the RAN 104/113, which may alsoinclude other base stations and/or network elements (not shown), such asa base station controller (BSC), a radio network controller (RNC), relaynodes, etc. The base station 114 a and/or the base station 114 b may beconfigured to transmit and/or receive wireless signals on one or morecarrier frequencies, which may be referred to as a cell (not shown).These frequencies may be in licensed spectrum, unlicensed spectrum, or acombination of licensed and unlicensed spectrum. A cell may providecoverage for a wireless service to a specific geographical area that maybe relatively fixed or that may change over time. The cell may furtherbe divided into cell sectors. For example, the cell associated with thebase station 114 a may be divided into three sectors. Thus, in oneembodiment, the base station 114 a may include three transceivers, i.e.,one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and mayutilize multiple transceivers for each sector of the cell. For example,beamforming may be used to transmit and/or receive signals in desiredspatial directions.

The base stations 114 a, 114 b may communicate with one or more of theWTRUs 102 a, 102 b, 102 c, 102 d over an air interface 116, which may beany suitable wireless communication link (e.g., radio frequency (RF),microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet(UV), visible light, etc.). The air interface 116 may be establishedusing any suitable radio access technology (RAT).

More specifically, as noted above, the communications system 100 may bea multiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. Forexample, the base station 114 a in the RAN 104/113 and the WTRUs 102 a,102 b, 102 c may implement a radio technology such as Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access (UTRA), whichmay establish the air interface 115/116/117 using wideband CDMA (WCDMA).WCDMA may include communication protocols such as High-Speed PacketAccess (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-SpeedDownlink (DL) Packet Access (HSDPA) and/or High-Speed UL Packet Access(HSUPA).

In an embodiment, the base station 114 a and the WTRUs 102 a, 102 b, 102c may implement a radio technology such as Evolved UMTS TerrestrialRadio Access (E-UTRA), which may establish the air interface 116 usingLong Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/orLTE-Advanced Pro (LTE-A Pro).

In an embodiment, the base station 114 a and the WTRUs 102 a, 102 b, 102c may implement a radio technology such as NR Radio Access, which mayestablish the air interface 116 using New Radio (NR).

In an embodiment, the base station 114 a and the WTRUs 102 a, 102 b, 102c may implement multiple radio access technologies. For example, thebase station 114 a and the WTRUs 102 a, 102 b, 102 c may implement LTEradio access and NR radio access together, for instance using dualconnectivity (DC) principles. Thus, the air interface utilized by WTRUs102 a, 102 b, 102 c may be characterized by multiple types of radioaccess technologies and/or transmissions sent to/from multiple types ofbase stations (e.g., an eNB and a gNB).

In other embodiments, the base station 114 a and the WTRUs 102 a, 102 b,102 c may implement radio technologies such as IEEE 802.11 (i.e.,Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperabilityfor Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO,Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), InterimStandard 856 (IS-856), Global System for Mobile communications (GSM),Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and thelike.

The base station 114 b in FIG. 1A may be a wireless router, Home Node B,Home eNode B, or access point, for example, and may utilize any suitableRAT for facilitating wireless connectivity in a localized area, such asa place of business, a home, a vehicle, a campus, an industrialfacility, an air corridor (e.g., for use by drones), a roadway, and thelike. In one embodiment, the base station 114 b and the WTRUs 102 c, 102d may implement a radio technology such as IEEE 802.11 to establish awireless local area network (WLAN). In an embodiment, the base station114 b and the WTRUs 102 c, 102 d may implement a radio technology suchas IEEE 802.15 to establish a wireless personal area network (WPAN). Inyet another embodiment, the base station 114 b and the WTRUs 102 c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE,LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. Asshown in FIG. 1A, the base station 114 b may have a direct connection tothe Internet 110. Thus, the base station 114 b may not be required toaccess the Internet 110 via the CN 106/115.

The RAN 104/113 may be in communication with the CN 106/115, which maybe any type of network configured to provide voice, data, applications,and/or voice over internet protocol (VoIP) services to one or more ofthe WTRUs 102 a, 102 b, 102 c, 102 d. The data may have varying qualityof service (QoS) requirements, such as differing throughputrequirements, latency requirements, error tolerance requirements,reliability requirements, data throughput requirements, mobilityrequirements, and the like. The CN 106/115 may provide call control,billing services, mobile location-based services, pre-paid calling,Internet connectivity, video distribution, etc., and/or performhigh-level security functions, such as user authentication. Although notshown in FIG. 1A, it will be appreciated that the RAN 104/113 and/or theCN 106/115 may be in direct or indirect communication with other RANsthat employ the same RAT as the RAN 104/113 or a different RAT. Forexample, in addition to being connected to the RAN 104/113, which may beutilizing a NR radio technology, the CN 106/115 may also be incommunication with another RAN (not shown) employing a GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

The CN 106/115 may also serve as a gateway for the WTRUs 102 a, 102 b,102 c, 102 d to access the PSTN 108, the Internet 110, and/or the othernetworks 112. The PSTN 108 may include circuit-switched telephonenetworks that provide plain old telephone service (POTS). The Internet110 may include a global system of interconnected computer networks anddevices that use common communication protocols, such as thetransmission control protocol (TCP), user datagram protocol (UDP) and/orthe internet protocol (IP) in the TCP/IP internet protocol suite. Thenetworks 112 may include wired and/or wireless communications networksowned and/or operated by other service providers. For example, thenetworks 112 may include another CN connected to one or more RANs, whichmay employ the same RAT as the RAN 104/113 or a different RAT.

Some or all of the WTRUs 102 a, 102 b, 102 c, 102 d in thecommunications system 100 may include multi-mode capabilities (e.g., theWTRUs 102 a, 102 b, 102 c, 102 d may include multiple transceivers forcommunicating with different wireless networks over different wirelesslinks). For example, the WTRU 102 c shown in FIG. 1A may be configuredto communicate with the base station 114 a, which may employ acellular-based radio technology, and with the base station 114 b, whichmay employ an IEEE 802 radio technology.

FIG. 1B is a system diagram illustrating an example WTRU 102. As shownin FIG. 1B, the WTRU 102 may include a processor 118, a transceiver 120,a transmit/receive element 122, a speaker/microphone 124, a keypad 126,a display/touchpad 128, non-removable memory 130, removable memory 132,a power source 134, a global positioning system (GPS) chipset 136,and/or other peripherals 138, among others. It will be appreciated thatthe WTRU 102 may include any sub-combination of the foregoing elementswhile remaining consistent with an embodiment.

The processor 118 may be a general purpose processor, a special purposeprocessor, a conventional processor, a digital signal processor (DSP), aplurality of microprocessors, one or more microprocessors in associationwith a DSP core, a controller, a microcontroller, Application SpecificIntegrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs)circuits, any other type of integrated circuit (IC), a state machine,and the like. The processor 118 may perform signal coding, dataprocessing, power control, input/output processing, and/or any otherfunctionality that enables the WTRU 102 to operate in a wirelessenvironment. The processor 118 may be coupled to the transceiver 120,which may be coupled to the transmit/receive element 122. While FIG. 1Bdepicts the processor 118 and the transceiver 120 as separatecomponents, it will be appreciated that the processor 118 and thetransceiver 120 may be integrated together in an electronic package orchip.

The transmit/receive element 122 may be configured to transmit signalsto, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment, thetransmit/receive element 122 may be an antenna configured to transmitand/or receive RF signals. In an embodiment, the transmit/receiveelement 122 may be an emitter/detector configured to transmit and/orreceive IR, UV, or visible light signals, for example. In yet anotherembodiment, the transmit/receive element 122 may be configured totransmit and/or receive both RF and light signals. It will beappreciated that the transmit/receive element 122 may be configured totransmit and/or receive any combination of wireless signals.

Although the transmit/receive element 122 is depicted in FIG. 1B as asingle element, the WTRU 102 may include any number of transmit/receiveelements 122. More specifically, the WTRU 102 may employ MIMOtechnology. Thus, in one embodiment, the WTRU 102 may include two ormore transmit/receive elements 122 (e.g., multiple antennas) fortransmitting and receiving wireless signals over the air interface 116.

The transceiver 120 may be configured to modulate the signals that areto be transmitted by the transmit/receive element 122 and to demodulatethe signals that are received by the transmit/receive element 122. Asnoted above, the WTRU 102 may have multi-mode capabilities. Thus, thetransceiver 120 may include multiple transceivers for enabling the WTRU102 to communicate via multiple RATs, such as NR and IEEE 802.11, forexample.

The processor 118 of the WTRU 102 may be coupled to, and may receiveuser input data from, the speaker/microphone 124, the keypad 126, and/orthe display/touchpad 128 (e.g., a liquid crystal display (LCD) displayunit or organic light-emitting diode (OLED) display unit). The processor118 may also output user data to the speaker/microphone 124, the keypad126, and/or the display/touchpad 128. In addition, the processor 118 mayaccess information from, and store data in, any type of suitable memory,such as the non-removable memory 130 and/or the removable memory 132.The non-removable memory 130 may include random-access memory (RAM),read-only memory (ROM), a hard disk, or any other type of memory storagedevice. The removable memory 132 may include a subscriber identitymodule (SIM) card, a memory stick, a secure digital (SD) memory card,and the like. In other embodiments, the processor 118 may accessinformation from, and store data in, memory that is not physicallylocated on the WTRU 102, such as on a server or a home computer (notshown).

The processor 118 may receive power from the power source 134, and maybe configured to distribute and/or control the power to the othercomponents in the WTRU 102. The power source 134 may be any suitabledevice for powering the WTRU 102. For example, the power source 134 mayinclude one or more dry cell batteries (e.g., nickel-cadmium (NiCd),nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion),etc.), solar cells, fuel cells, and the like.

The processor 118 may also be coupled to the GPS chipset 136, which maybe configured to provide location information (e.g., longitude andlatitude) regarding the current location of the WTRU 102. In additionto, or in lieu of, the information from the GPS chipset 136, the WTRU102 may receive location information over the air interface 116 from abase station (e.g., base stations 114 a, 114 b) and/or determine itslocation based on the timing of the signals being received from two ormore nearby base stations. It will be appreciated that the WTRU 102 mayacquire location information by way of any suitablelocation-determination method while remaining consistent with anembodiment.

The processor 118 may further be coupled to other peripherals 138, whichmay include one or more software and/or hardware modules that provideadditional features, functionality and/or wired or wirelessconnectivity. For example, the peripherals 138 may include anaccelerometer, an e-compass, a satellite transceiver, a digital camera(for photographs and/or video), a universal serial bus (USB) port, avibration device, a television transceiver, a hands free headset, aBluetooth® module, a frequency modulated (FM) radio unit, a digitalmusic player, a media player, a video game player module, an Internetbrowser, a Virtual Reality and/or Augmented Reality (VR/AR) device, anactivity tracker, and the like. The peripherals 138 may include one ormore sensors, the sensors may be one or more of a gyroscope, anaccelerometer, a hall effect sensor, a magnetometer, an orientationsensor, a proximity sensor, a temperature sensor, a time sensor; ageolocation sensor; an altimeter, a light sensor, a touch sensor, amagnetometer, a barometer, a gesture sensor, a biometric sensor, and/ora humidity sensor.

The WTRU 102 may include a full duplex radio for which transmission andreception of some or all of the signals (e.g., associated withparticular subframes for both the UL (e.g., for transmission) anddownlink (e.g., for reception) may be concurrent and/or simultaneous.The full duplex radio may include an interference management unit 139 toreduce and or substantially eliminate self-interference via eitherhardware (e.g., a choke) or signal processing via a processor (e.g., aseparate processor (not shown) or via processor 118). In an embodiment,the WTRU 102 may include a half-duplex radio for which transmission andreception of some or all of the signals (e.g., associated withparticular subframes for either the UL (e.g., for transmission) or thedownlink (e.g., for reception)).

FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106according to an embodiment. As noted above, the RAN 104 may employ anE-UTRA radio technology to communicate with the WTRUs 102 a, 102 b, 102c over the air interface 116. The RAN 104 may also be in communicationwith the CN 106.

The RAN 104 may include eNode-Bs 160 a, 160 b, 160 c, though it will beappreciated that the RAN 104 may include any number of eNode-Bs whileremaining consistent with an embodiment. The eNode-Bs 160 a, 160 b, 160c may each include one or more transceivers for communicating with theWTRUs 102 a, 102 b, 102 c over the air interface 116. In one embodiment,the eNode-Bs 160 a, 160 b, 160 c may implement MIMO technology. Thus,the eNode-B 160 a, for example, may use multiple antennas to transmitwireless signals to, and/or receive wireless signals from, the WTRU 102a.

Each of the eNode-Bs 160 a, 160 b, 160 c may be associated with aparticular cell (not shown) and may be configured to handle radioresource management decisions, handover decisions, scheduling of usersin the UL and/or DL, and the like. As shown in FIG. 1C, the eNode-Bs 160a, 160 b, 160 c may communicate with one another over an X2 interface.

The CN 106 shown in FIG. 1C may include a mobility management entity(MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN)gateway (or PGW) 166. While each of the foregoing elements are depictedas part of the CN 106, it will be appreciated that any of these elementsmay be owned and/or operated by an entity other than the CN operator.

The MME 162 may be connected to each of the eNode-Bs 162 a, 162 b, 162 cin the RAN 104 via an S1 interface and may serve as a control node. Forexample, the MME 162 may be responsible for authenticating users of theWTRUs 102 a, 102 b, 102 c, bearer activation/deactivation, selecting aparticular serving gateway during an initial attach of the WTRUs 102 a,102 b, 102 c, and the like. The MME 162 may provide a control planefunction for switching between the RAN 104 and other RANs (not shown)that employ other radio technologies, such as GSM and/or WCDMA.

The SGW 164 may be connected to each of the eNode Bs 160 a, 160 b, 160 cin the RAN 104 via the S1 interface. The SGW 164 may generally route andforward user data packets to/from the WTRUs 102 a, 102 b, 102 c. The SGW164 may perform other functions, such as anchoring user planes duringinter-eNode B handovers, triggering paging when DL data is available forthe WTRUs 102 a, 102 b, 102 c, managing and storing contexts of theWTRUs 102 a, 102 b, 102 c, and the like.

The SGW 164 may be connected to the PGW 166, which may provide the WTRUs102 a, 102 b, 102 c with access to packet-switched networks, such as theInternet 110, to facilitate communications between the WTRUs 102 a, 102b, 102 c and IP-enabled devices.

The CN 106 may facilitate communications with other networks. Forexample, the CN 106 may provide the WTRUs 102 a, 102 b, 102 c withaccess to circuit-switched networks, such as the PSTN 108, to facilitatecommunications between the WTRUs 102 a, 102 b, 102 c and traditionalland-line communications devices. For example, the CN 106 may include,or may communicate with, an IP gateway (e.g., an IP multimedia subsystem(IMS) server) that serves as an interface between the CN 106 and thePSTN 108. In addition, the CN 106 may provide the WTRUs 102 a, 102 b,102 c with access to the other networks 112, which may include otherwired and/or wireless networks that are owned and/or operated by otherservice providers.

Although the WTRU is described in FIGS. 1A-1D as a wireless terminal, itis contemplated that in certain representative embodiments that such aterminal may use (e.g., temporarily or permanently) wired communicationinterfaces with the communication network.

In representative embodiments, the other network 112 may be a WLAN.

A WLAN in Infrastructure Basic Service Set (BSS) mode may have an AccessPoint (AP) for the BSS and one or more stations (STAs) associated withthe AP. The AP may have an access or an interface to a DistributionSystem (DS) or another type of wired/wireless network that carriestraffic in to and/or out of the BSS. Traffic to STAs that originatesfrom outside the BSS may arrive through the AP and may be delivered tothe STAs. Traffic originating from STAs to destinations outside the BSSmay be sent to the AP to be delivered to respective destinations.Traffic between STAs within the BSS may be sent through the AP, forexample, where the source STA may send traffic to the AP and the AP maydeliver the traffic to the destination STA. The traffic between STAswithin a BSS may be considered and/or referred to as peer-to-peertraffic. The peer-to-peer traffic may be sent between (e.g., directlybetween) the source and destination STAs with a direct link setup (DLS).In certain representative embodiments, the DLS may use an 802.11e DLS oran 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS)mode may not have an AP, and the STAs (e.g., all of the STAs) within orusing the IBSS may communicate directly with each other. The IBSS modeof communication may sometimes be referred to herein as an “ad-hoc” modeof communication.

When using the 802.11ac infrastructure mode of operation or a similarmode of operations, the AP may transmit a beacon on a fixed channel,such as a primary channel. The primary channel may be a fixed width(e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling.The primary channel may be the operating channel of the BSS and may beused by the STAs to establish a connection with the AP. In certainrepresentative embodiments, Carrier Sense Multiple Access with CollisionAvoidance (CSMA/CA) may be implemented, for example in in 802.11systems. For CSMA/CA, the STAs (e.g., every STA), including the AP, maysense the primary channel. If the primary channel is sensed/detectedand/or determined to be busy by a particular STA, the particular STA mayback off. One STA (e.g., only one station) may transmit at any giventime in a given BSS.

High Throughput (HT) STAs may use a 40 MHz wide channel forcommunication, for example, via a combination of the primary 20 MHzchannel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHzwide channel.

Very High Throughput (VHT) STAs may support 20 MHz, 40 MHz, 80 MHz,and/or 160 MHz wide channels. The 40 MHz, and/or 80 MHz, channels may beformed by combining contiguous 20 MHz channels. A 160 MHz channel may beformed by combining 8 contiguous 20 MHz channels, or by combining twonon-contiguous 80 MHz channels, which may be referred to as an 80+80configuration. For the 80+80 configuration, the data, after channelencoding, may be passed through a segment parser that may divide thedata into two streams. Inverse Fast Fourier Transform (IFFT) processing,and time domain processing, may be done on each stream separately. Thestreams may be mapped on to the two 80 MHz channels, and the data may betransmitted by a transmitting STA. At the receiver of the receiving STA,the above described operation for the 80+80 configuration may bereversed, and the combined data may be sent to the Medium Access Control(MAC).

Sub 1 GHz modes of operation are supported by 802.11af and 802.11ah. Thechannel operating bandwidths, and carriers, are reduced in 802.11af and802.11ah relative to those used in 802.11n, and 802.11ac. 802.11afsupports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space(TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and16 MHz bandwidths using non-TVWS spectrum. According to a representativeembodiment, 802.11ah may support Meter Type Control/Machine-TypeCommunications, such as MTC devices in a macro coverage area. MTCdevices may have certain capabilities, for example, limited capabilitiesincluding support for (e.g., only support for) certain and/or limitedbandwidths. The MTC devices may include a battery with a battery lifeabove a threshold (e.g., to maintain a very long battery life).

WLAN systems, which may support multiple channels, and channelbandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include achannel which may be designated as the primary channel. The primarychannel may have a bandwidth equal to the largest common operatingbandwidth supported by all STAs in the BSS. The bandwidth of the primarychannel may be set and/or limited by a STA, from among all STAs inoperating in a BSS, which supports the smallest bandwidth operatingmode. In the example of 802.11ah, the primary channel may be 1 MHz widefor STAs (e.g., MTC type devices) that support (e.g., only support) a 1MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes.Carrier sensing and/or Network Allocation Vector (NAV) settings maydepend on the status of the primary channel. If the primary channel isbusy, for example, due to a STA (which supports only a 1 MHz operatingmode), transmitting to the AP, the entire available frequency bands maybe considered busy even though a majority of the frequency bands remainsidle and may be available.

In the United States, the available frequency bands, which may be usedby 802.11ah, are from 902 MHz to 928 MHz. In Korea, the availablefrequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the availablefrequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidthavailable for 802.11ah is 6 MHz to 26 MHz depending on the country code.

FIG. 1D is a system diagram illustrating the RAN 113 and the CN 115according to an embodiment. As noted above, the RAN 113 may employ an NRradio technology to communicate with the WTRUs 102 a, 102 b, 102 c overthe air interface 116. The RAN 113 may also be in communication with theCN 115.

The RAN 113 may include gNBs 180 a, 180 b, 180 c, though it will beappreciated that the RAN 113 may include any number of gNBs whileremaining consistent with an embodiment. The gNBs 180 a, 180 b, 180 cmay each include one or more transceivers for communicating with theWTRUs 102 a, 102 b, 102 c over the air interface 116. In one embodiment,the gNBs 180 a, 180 b, 180 c may implement MIMO technology. For example,gNBs 180 a, 180 b may utilize beamforming to transmit signals to and/orreceive signals from the gNBs 180 a, 180 b, 180 c. Thus, the gNB 180 a,for example, may use multiple antennas to transmit wireless signals to,and/or receive wireless signals from, the WTRU 102 a. In an embodiment,the gNBs 180 a, 180 b, 180 c may implement carrier aggregationtechnology. For example, the gNB 180 a may transmit multiple componentcarriers to the WTRU 102 a (not shown). A subset of these componentcarriers may be on unlicensed spectrum while the remaining componentcarriers may be on licensed spectrum. In an embodiment, the gNBs 180 a,180 b, 180 c may implement Coordinated Multi-Point (CoMP) technology.For example, WTRU 102 a may receive coordinated transmissions from gNB180 a and gNB 180 b (and/or gNB 180 c).

The WTRUs 102 a, 102 b, 102 c may communicate with gNBs 180 a, 180 b,180 c using transmissions associated with a scalable numerology. Forexample, the OFDM symbol spacing and/or OFDM subcarrier spacing may varyfor different transmissions, different cells, and/or different portionsof the wireless transmission spectrum. The WTRUs 102 a, 102 b, 102 c maycommunicate with gNBs 180 a, 180 b, 180 c using subframe or transmissiontime intervals (TTIs) of various or scalable lengths (e.g., containingvarying number of OFDM symbols and/or lasting varying lengths ofabsolute time).

The gNBs 180 a, 180 b, 180 c may be configured to communicate with theWTRUs 102 a, 102 b, 102 c in a standalone configuration and/or anon-standalone configuration. In the standalone configuration, WTRUs 102a, 102 b, 102 c may communicate with gNBs 180 a, 180 b, 180 c withoutalso accessing other RANs (e.g., such as eNode-Bs 160 a, 160 b, 160 c).In the standalone configuration, WTRUs 102 a, 102 b, 102 c may utilizeone or more of gNBs 180 a, 180 b, 180 c as a mobility anchor point. Inthe standalone configuration, WTRUs 102 a, 102 b, 102 c may communicatewith gNBs 180 a, 180 b, 180 c using signals in an unlicensed band. In anon-standalone configuration WTRUs 102 a, 102 b, 102 c may communicatewith/connect to gNBs 180 a, 180 b, 180 c while also communicatingwith/connecting to another RAN such as eNode-Bs 160 a, 160 b, 160 c. Forexample, WTRUs 102 a, 102 b, 102 c may implement DC principles tocommunicate with one or more gNBs 180 a, 180 b, 180 c and one or moreeNode-Bs 160 a, 160 b, 160 c substantially simultaneously. In thenon-standalone configuration, eNode-Bs 160 a, 160 b, 160 c may serve asa mobility anchor for WTRUs 102 a, 102 b, 102 c and gNBs 180 a, 180 b,180 c may provide additional coverage and/or throughput for servicingWTRUs 102 a, 102 b, 102 c.

Each of the gNBs 180 a, 180 b, 180 c may be associated with a particularcell (not shown) and may be configured to handle radio resourcemanagement decisions, handover decisions, scheduling of users in the ULand/or DL, support of network slicing, dual connectivity, interworkingbetween NR and E-UTRA, routing of user plane data towards User PlaneFunction (UPF) 184 a, 184 b, routing of control plane informationtowards Access and Mobility Management Function (AMF) 182 a, 182 b andthe like. As shown in FIG. 1D, the gNBs 180 a, 180 b, 180 c maycommunicate with one another over an Xn interface.

The CN 115 shown in FIG. 1D may include at least one AMF 182 a, 182 b,at least one UPF 184 a, 184 b, at least one Session Management Function(SMF) 183 a, 183 b, and possibly a Data Network (DN) 185 a, 185 b. Whileeach of the foregoing elements are depicted as part of the CN 115, itwill be appreciated that any of these elements may be owned and/oroperated by an entity other than the CN operator.

The AMF 182 a, 182 b may be connected to one or more of the gNBs 180 a,180 b, 180 c in the RAN 113 via an N2 interface and may serve as acontrol node. For example, the AMF 182 a, 182 b may be responsible forauthenticating users of the WTRUs 102 a, 102 b, 102 c, support fornetwork slicing (e.g., handling of different PDU sessions with differentrequirements), selecting a particular SMF 183 a, 183 b, management ofthe registration area, termination of Non-Access Stratum (NAS)signaling, mobility management, and the like. Network slicing may beused by the AMF 182 a, 182 b in order to customize CN support for WTRUs102 a, 102 b, 102 c based on the types of services being utilized WTRUs102 a, 102 b, 102 c. For example, different network slices may beestablished for different use cases such as services relying onultra-reliable low latency (URLLC) access, services relying on enhancedmassive mobile broadband (eMBB) access, services for machine typecommunication (MTC) access, and/or the like. The AMF 162 may provide acontrol plane function for switching between the RAN 113 and other RANs(not shown) that employ other radio technologies, such as LTE, LTE-A,LTE-A Pro, and/or non-3GPP access technologies such as WiFi.

The SMF 183 a, 183 b may be connected to an AMF 182 a, 182 b in the CN115 via an N11 interface. The SMF 183 a, 183 b may also be connected toa UPF 184 a, 184 b in the CN 115 via an N4 interface. The SMF 183 a, 183b may select and control the UPF 184 a, 184 b and configure the routingof traffic through the UPF 184 a, 184 b. The SMF 183 a, 183 b mayperform other functions, such as managing and allocating UE IP address,managing PDU sessions, controlling policy enforcement and QoS, providingdownlink data notifications, and the like. A PDU session type may beIP-based, non-IP based, Ethernet-based, and the like.

The UPF 184 a, 184 b may be connected to one or more of the gNBs 180 a,180 b, 180 c in the RAN 113 via an N3 interface, which may provide theWTRUs 102 a, 102 b, 102 c with access to packet-switched networks, suchas the Internet 110, to facilitate communications between the WTRUs 102a, 102 b, 102 c and IP-enabled devices. The UPF 184, 184 b may performother functions, such as routing and forwarding packets, enforcing userplane policies, supporting multi-homed PDU sessions, handling user planeQoS, buffering downlink packets, providing mobility anchoring, and thelike.

The CN 115 may facilitate communications with other networks. Forexample, the CN 115 may include, or may communicate with, an IP gateway(e.g., an IP multimedia subsystem (IMS) server) that serves as aninterface between the CN 115 and the PSTN 108. In addition, the CN 115may provide the WTRUs 102 a, 102 b, 102 c with access to the othernetworks 112, which may include other wired and/or wireless networksthat are owned and/or operated by other service providers. In oneembodiment, the WTRUs 102 a, 102 b, 102 c may be connected to a localData Network (DN) 185 a, 185 b through the UPF 184 a, 184 b via the N3interface to the UPF 184 a, 184 b and an N6 interface between the UPF184 a, 184 b and the DN 185 a, 185 b.

In view of FIGS. 1A-1D, and the corresponding description of FIGS.1A-1D, one or more, or all, of the functions described herein withregard to one or more of: WTRU 102 a-d, Base Station 114 a-b, eNode-B160 a-c, MME 162, SGW 164, PGW 166, gNB 180 a-c, AMF 182 a-b, UPF 184a-b, SMF 183 a-b, DN 185 a-b, and/or any other device(s) describedherein, may be performed by one or more emulation devices (not shown).The emulation devices may be one or more devices configured to emulateone or more, or all, of the functions described herein. For example, theemulation devices may be used to test other devices and/or to simulatenetwork and/or WTRU functions.

The emulation devices may be designed to implement one or more tests ofother devices in a lab environment and/or in an operator networkenvironment. For example, the one or more emulation devices may performthe one or more, or all, functions while being fully or partiallyimplemented and/or deployed as part of a wired and/or wirelesscommunication network in order to test other devices within thecommunication network. The one or more emulation devices may perform theone or more, or all, functions while being temporarilyimplemented/deployed as part of a wired and/or wireless communicationnetwork. The emulation device may be directly coupled to another devicefor purposes of testing and/or may performing testing using over-the-airwireless communications.

The one or more emulation devices may perform the one or more, includingall, functions while not being implemented/deployed as part of a wiredand/or wireless communication network. For example, the emulationdevices may be utilized in a testing scenario in a testing laboratoryand/or a non-deployed (e.g., testing) wired and/or wirelesscommunication network in order to implement testing of one or morecomponents. The one or more emulation devices may be test equipment.Direct RF coupling and/or wireless communications via RF circuitry(e.g., which may include one or more antennas) may be used by theemulation devices to transmit and/or receive data.

Positioning in 3GPP Release 16

3GPP Rel-16 for NR (New Radio) supports positioning for RRC_CONNECTEDmode. During IDLE or INACTIVE mode, positioning procedure, or WTRUbehavior is unknown.

To reduce power consumption, WTRUs need to be in INACTIVE or IDLE mode.In addition, recent demands for centimeter level accuracy for IIoT(Industrial Internet of Things) applications require both high accuracyand low latency during positioning. This specification discloses methodsand apparatus that satisfy the requirements for high accuracy and lowlatency even when WTRUs are in INACTIVE/IDLE mode.

In the current 3GPP specification, configurations of reference signalsused for positioning during IDLE and INACTIVE mode are not specified. Inaddition, procedures for a WTRU to obtain reference signalconfigurations or measurement reporting is not clear. IIoT devices suchas sensors or cameras may be accidently moved from their currentpositions, e.g., a sensor may be dislodged from its mount and carried byflooding or strong winds to different areas. Therefore, mobilitysupport, which reduces latency during positioning, is needed forpositioning during INACTIVE/IDLE mode. Further, IIoT applications mayneed to support large numbers of IIoT devices, and hence features tosupport simultaneous positioning are needed.

Herein, “SRS for positioning” refers to an SRS signal/transmission usedfor positioning. Resources for SRS for positioning may be defined (e.g.,signaled) by RRC. Rel. 16 specifies SRS resource set and SRS resourceconfigured for positioning. However, “SRS for positioning” or “SRS” asused in this disclosure may include at least one of the following:

-   -   SRS which is configured under SRS-PosResourceSet-r16 and        SRS-PosResource-r16 in [2]    -   SRS which is configured under SRS-ResourceSet and SRS-Resource        in [2]    -   SRS which is not configured under SRS-PosResourceSet-r16 and        SRS-PosResource-r16 in [2]    -   SRS which is not configured under SRS-ResourceSet and        SRS-Resource in [2]    -   SRS which is not associated with SRS-PosResourceSet-r16,        SRS-PosResource-r16, SRS-ResourceSet or SRS-Resource in [2]    -   Uplink reference signal that is associated for positioning    -   DM-RS for uplink    -   PTRS for uplink

For brevity, SRS for positioning is denoted as “SRSp” herein, and PRS orSRS as used herein are not limited to RS used for positioning. Themethods and apparatus disclosed herein can be applied to or used withany DL or UL reference signals.

Configurations and WTRU Behavior During a RACH Procedure Trigger forPositioning Positioning Configuration

A positioning configuration may include a set of information related topositioning measurement and/or SRSp transmission. One or more offollowing types of information may be included in a positioningconfiguration:

-   -   One or more of positioning method used (e.g., DL-TDOA (Time        Difference of Arrival), UL-TDOA, DL-AoD (Angle of Departure),        UL-AoA (Angle of Arrival), Multi-RTT)    -   PRS configuration    -   SRSp configuration    -   Uplink resource (e.g., Physical Random Access Channel (PRACH),        Physical Uplink Shared Channel (PUSCH), Physical Uplink Control        Channel (PUCCH)) to report the positioning measurement    -   One or more threshold values to determine the positioning        measurement quality    -   Positioning mode of operation (e.g., starting positioning mode        of operation)

PRS resource configuration may include any one or more of the following:

-   -   PRS resource ID    -   PRS sequence ID, or other IDs used to generate PRS sequence    -   PRS resource element offset    -   PRS resource slot offset    -   PRS symbol offset    -   PRS Quasi Co-location Information (QCL) information    -   PRS resource set ID    -   List of PRS resources in the resource set    -   Number of PRS symbols    -   Muting pattern for PRS, muting parameters such as repetition        factor, muting options    -   PRS resource power    -   Periodicity of PRS transmission    -   Spatial direction information of PRS transmission (e.g., beam        information, angles of transmission)    -   Spatial direction information of UL Reference Signal (RS)        reception (e.g., beam ID used to receive UL RS, angle of        arrival)

SRSp resources configuration may include at least one of the following:

-   -   Resource ID    -   Comb offset values, cyclic shift values    -   Start position in the frequency domain    -   Number of SRSp symbols    -   Shift in the frequency domain for SRSp    -   Frequency hopping pattern    -   Type of SRSp, e.g., aperiodic, semi-persistent or periodic    -   Sequence ID used to generate SRSp, or other IDs used to generate        SRSp sequence    -   Spatial relation information, indicating which reference signal        the SRSp is related to spatially    -   Resource set ID    -   List of SRSp resources in the resource set    -   Transmission power related information    -   Pathloss reference information which may contain index for        Synchronization Signal Block (SSB), Channel State Information        Reference Signal (CSI-RS) or PRS    -   Periodicity of SRSp transmission    -   Spatial direction information of SRSp transmission (e.g., beam        information, angles of transmission)    -   Spatial direction information of DL RS reception (e.g., beam ID        used to receive DL RS, angle of arrival)

As the part of its configuration, the WTRU may receive informationrelated to the cell ID, global cell ID, or TRP ID which is associatedwith PRS. For example, the TRP which transmits PRS is identified by theTRP ID, which may belong to a cell identified by the cell ID. The WTRUmay be configured with timing information such as System Frame Number(SFN) offset for PRS or SRSp transmission. The offset is introduced toprevent the WTRU from receiving overlapping PRS in the time domain.

In one method, the WTRU may be configured with measurement gaps toreceive PRS from the network.

Positioning Mode of Operation and Conditions for Occurrence ofPositioning Mode

In one embodiment, a WTRU may be configured, determined, or indicated toperform positioning measurement in RRC idle mode and/or RRC inactivemode. For example, one or more of the positioning modes of operation maybe used. In a first positioning mode of operation, a WTRU may performpositioning measurement and reporting when the WTRU is in RRC connectedmode; in a second positioning mode of operation, a WTRU may performpositioning measurement and reporting in one or more RRC connectionstates (e.g., connected, inactive, and idle). One or more of thefollowing may apply:

-   -   A WTRU may indicate its capability to support the positioning        mode of operation to an LMF. For example, a first WTRU may        indicate its capability to support a first positioning mode of        operation only, while a second WTRU may indicate its capability        to support a first and second positioning modes of operation    -   The positioning mode of operation may be configured or indicated        (e.g., by LMF)    -   The positioning mode of operation may be determined based on the        WTRU power status. For example, if a WTRU is in a low power        status (e.g., remaining battery level is lower than a        threshold), the WTRU may perform a first positioning mode of        operation (e.g., positioning measurement and reporting only in        RRC connected status); otherwise, the WTRU may perform a second        positioning mode of operation (e.g., positioning measurement and        reporting at least in RRC connected/inactive states or RRC        connected/inactive/idle states)    -   The positioning mode of operation may be determined based on an        application type (or use case), wherein the application type (or        use case) may be at least one of enhanced Mobile Broadband        (eMBB), Ultra-Reliable and Low Latency Communications (URLLC),        IIoT, public safety, V2X, and massive machine type        communications (mMTC))        -   Application type may be interchangeably used with use case,            traffic type, device type, target QoS, QoS, requirements,            and WTRU category        -   A first positioning mode of operation may be used for            application types that may not require high reliability            and/or low latency and a second positioning mode of            operation may be used for application types that may require            high reliability and/or low latency    -   The positioning mode of operation may be determined based on the        availability of other positioning signals (e.g., Global        Navigation Satellite System (GNSS), WiFi signal). For example, a        first positioning mode of operation may be used when another        positioning signal (e.g., GNSS) is available, while a second        positioning mode of operation may be used when another        positioning signal is not available        -   In this case, it is assumed that positioning accuracy may be            reasonably sufficient even without a RAN-based positioning            method when a WTRU is in RRC inactive or RRC idle status    -   The positioning mode of operation may be determined based on the        positioning measurement accuracy. The positioning measurement        accuracy may be interchangeably used with positioning        measurement reliability and positioning measurement quality        -   In an example, if the positioning measurement accuracy            (e.g., RSRP level of a PRS measurement) is lower than a            threshold, the WTRU may perform a first positioning mode of            operation; otherwise, the WTRU may perform a second            positioning mode of operation        -   In another example, if there is a Line of Sight (LoS) path            for the positioning measurement, the WTRU may perform a            first positioning mode of operation; otherwise, the WTRU may            perform a second positioning mode of operation        -   The positioning measurement accuracy metric may include at            least one of RSRP, L1-RSRP, existence of LoS path, beam            quality, number of beams used for PRS transmission, etc.

A WTRU may switch positioning mode of operation when one or morepredefined conditions are met. For example, a WTRU may perform a firstpositioning mode of operation when the positioning measurement accuracyis lower than a threshold. When the positioning measurement accuracybecomes better and above threshold, the WTRU may switch to a secondpositioning mode of operation.

The WTRU may request to switch to a second positioning mode of operationfrom a first positioning mode of operation (e.g., to LMF)

Using DRX to Determine when to Wake up to Perform PositioningMeasurements

In one method, a WTRU may wake up for a positioning occasion in DRX,which is referred to as a DRX positioning occasion to performmeasurements and/or report positioning related data. A DRX positioningoccasion may include: on durations, a subset of DRX off cycles, a subsetof on durations if a WTRU identity has been determined to be signaled inthe on duration (e.g., in P-RNTI or power savings RNTI (Radio NetworkTemporary Identifier), and/or a subset of on durations if the WTRU hasreceived a wake up signal.

A WTRU may be configured with a specific RNTI or a group RNTI, which canbe used to indicate to the WTRU (or a group of WTRUs) to wake up toperform positioning measurements and/or reporting. The WTRU maydetermine the configuration of PRS or SRSp (including contents ofapplicable resource sets, resources, and the sequence ID) from thereceived RNTI, from PDSCH transmission addressed to that RNTI, or fromthe paging message itself. The WTRU may also receive an uplink grantalong with the configuration to provide the associated positioningreport.

In inactive sate, the WTRU may monitor the PDCCH during on durationaddressed to I-RNTI or C-RNTI for the reception of the indication forpositioning.

Upon reception of an indication for positioning in a paging occasion,the WTRU may determine the related configuration for PRS or SRSp,perform the related positioning measurements, and/or report the relatedposition or positioning report (part of a PUSCH transmission in a RACHprocedure or on a configured grant applicable in the current servingcell).

WTRU in Idle/Inactive Mode Initiates a Positioning Procedure Based on aReception/Detection of a Positioning Related Trigger

In various embodiments, the WTRU may receive a trigger for initiating apositioning procedure for different RAT-dependent positioning methods(e.g., DL-based, UL-based or UL and DL based positioning) whileremaining in idle/inactive mode. For example, the triggerreceived/detected by the WTRU may contain information on the WTRU ID,identifier of positioning method, and identifier of theselected/activated PRS/SRSp configurations. The configurations relatedto the positioning methods, including the PRS/SRSp (pre)configurations,may be received by the WTRU either prior to transitioning or whileoperating in idle/inactive mode.

The triggering conditions for a WTRU in idle/inactive mode forinitiating positioning operation (e.g., measurement of DL PRS ortransmission of SRSp) and/or for receiving the PRS/SRSp configurations)may be one or more of the following:

-   -   Higher layer/application trigger: For example, in the case of        WTRU-based positioning, the higher layers in the WTRU may        trigger reception of the PRS configuration (e.g., assistance        information in SIB) or trigger the transmission of a request        message for receiving PRS/SRSp configuration. In this case, if        the WTRU is pre-configured with the PRS/SRSp configurations and        the pre-configured PRS/SRSp are valid when triggered by a higher        layer function (e.g. PRS/SRSp configurations may be considered        to be valid if the timing and/or cell area list information        associated with the PSRS/SRSp configurations is within the        validity time and/or validity cell area bounds) the WTRU may use        the existing PRS/SRSp configurations for positioning, for        example. Otherwise, the WTRU may send an indication message to        the LMF/RAN requesting the PRS/SRSp configurations.    -   Network trigger: For example, in the case of WTRU assisted        positioning, the trigger for receiving the PRS configuration        and/or for initiating the measurement of DL PRS may be received        from the LMF or RAN either in a Core Network (CN) paging message        or a System Information Block (SIB). Likewise, the trigger for        receiving the SRSp configuration and/or for initiating the        transmission of UL SRSp may be received from the RAN either in a        RAN paging message or SIB, for example.    -   SIB: For example, the WTRU may be triggered to receive PRS/SRSp        configurations or to update the existing PRS/SRSp based on the        reception of a SIB while in idle/inactive mode.    -   Paging: For example, the WTRU may be triggered to initiate PRS        measurement or SRSp transmission upon receiving a CN or RAN        paging message

In WTRU-based positioning, upon receiving the trigger from a higherlayer/application while in idle/inactive mode, the WTRU may apply thereceived/available PRS configurations for DL-based positioning, SRSpconfiguration for UL-based positioning, or both PRS and SRSp for UL andDL-based positioning. For the DL positioning, the WTRU may provide themeasurement report determined by measuring the downlink PRS directly tothe upper layers. For UL based and UL and DL based positioning, the WTRUmay receive the measurement reports from the RAN upon sending the SRSp.The received measurement reports and, possibly the calculatedpositioning information, are subsequently sent to the upper layers.

In WTRU-assisted positioning, the trigger for requesting WTRU locationmay be received from the LMF, and the WTRU may apply thereceived/available PRS configuration for DL-based positioning, SRSpconfiguration for UL-based positioning, or both PRS and SRSp for UL andDL based positioning. For the DL-based positioning, the WTRU may send tothe LMF the measurement reports determined by measuring the downlinkPRS. For UL-based and UL and DL based positioning, the WTRU may transmitthe SRSp to RAN, which subsequently forwards the measurement reports tothe LMF.

With the above methods, the WTRU can start the positioning processduring IDLE or INACTIVE mode, allowing the WTRU to reduce powerconsumption.

Configurations/Reconfigurations Receiving the Configuration of SRSp orPRS in IDLE or Inactive States

The WTRU may determine and receive a configuration associated withpositioning measurements and reporting from broadcast signaling fromstored configurations that are part of the WTRU context, and/or byrequesting it in a RACH procedure. If configuration of positioningmeasurement resources (e.g., PRS, SRSp, and/or associated parameters andsequence IDs) is known to the WTRU, the WTRU may report associatedpositioning measurements, the WTRU position, and/or a positioning reportpart of a RACH procedure or on a Configured Grant (CG) applicable in theserving cell. If the WTRU does not have such configuration(s), the WTRUmay initiate a new RACH procedure to obtain the configuration associatedwith positioning measurements and reporting.

The WTRU may obtain the resource configuration(s) for PRS and/or SRSp inMsg2, Msg4 or MsgB. The WTRU may perform positioning measurements andthen report them (e.g., the WTRU position or positioning relatedmeasurements in WTRU-assisted mode) in part of Msg3/A, a grant scheduledby the gNB and provided part of MsgB or Msg4, a grant scheduled by thegNB after the completion of the RACH procedure (e.g., Msg 5), and/or anuplink configured grant.

The configuration of positioning measurements may also include asequence ID for PRS and/or SRSp, which may be unique to the WTRU or anyWTRU that used the same PRACH resource. In the absence of such sequenceID, the WTRU may use a previously used sequence ID (e.g., used inconnected mode or the last used sequence ID), use a default sequence ID,and/or use a random sequence ID, possibly determined from the WTRUidentity or the resource identity (e.g., I-RNTI, C-RNTI, RA-RNTI,MsgB-RNTI, small data RNTI, paging RNTI, or CS-RNTI).

The WTRU may also combine a configuration received by broadcastsignaling with a configuration obtained using the paging procedure orthe RACH procedure to determine the full configuration of PRS or SRSp(including applicable resources and the sequence ID). For example,broadcast signaling can indicate the positioning resource allocationwhile the paging indication (e.g., in Physical Downlink Shared Channel(PDSCH) or Physical Downlink Control Channel (PDCCH)) may includeremaining WTRU-specific parameters (e.g., sequence ID, scramblingidentities, security keys) used for positioning. Broadcast signaling mayalso provide a minimal subset of configurations needed to obtain theremaining configurations (e.g., in PDSCH after paging or part of a RACHprocedure).

In one embodiment, the WTRU may be configured with the scramblingidentify with which the WTRU can descramble the PRS sequence. Thescrambling ID may be used by the network to randomize the PRS sequencesuch that if the number of WTRUs the network tries to locate is large,the network may use a scrambling ID to randomize the PRS sequence suchthat only the WTRU that is configured with the scrambling ID candescramble the PRS. If the WTRU does not have the scrambling ID andattempts to descramble the PRS, the resulting PRS appears as noise.

How Timing Advance is Obtained for SRSp

The WTRU may obtain TA (timing advance) used for SRSp transmission fromthe RACH procedure. The WTRU may receive the TA in message 2 sent fromthe network in the 4-step RACH procedure. In another method, if 2-stepRACH is conducted, rather than 4-step RACH, the WTRU may assume that theTA that it has is zero. This assumption is reasonable because an RSRPfor the measured SSB that is sufficiently high to permit 2-step RACHsuggests that the WTRU is close to the TRP, and there is no need toperform timing adjustment. Thus, the WTRU can assume that TA is nearlyzero. In addition, the WTRU may receive IDLE/INACTIVE mode specific TAfor SRSp transmission in the PDCCH or PDSCH. The WTRU may receive the TArelated to SRSp transmission in RRCRelease or RRC or MAC-CE. The WTRUmay determine to apply the TA prior to the SRSp transmission foraccurate time alignment.

Configuration Message for Positioning

The WTRU may receive a configuration message for positioning (e.g.,configuration of SRSp, PRS, and/or resource applicable for positioningreporting) as part of RRC release message, part of the WTRU contexttransfer, or in an RRC or LTE Positioning Protocol (LPP) configurationmessage, e.g., upon transitioning into INACTIVE state or within INACTIVEstate itself. Such configuration message can be received in connectedmode. Such configuration message can be received in Msg4 or MsgB or inany PDSCH transmission in INACTIVE state. The configuration message (RRCor LPP message) can contain at least one or more of: resource allocationfor SRSp, resource allocation for PRS, indication of which Small DataTransmission (SDT) resource are applicable for reporting a positioningreport (e.g. CG and/or RACH resources), an on-demand or temporarypositioning resource or reference signal, and/or resource allocation forresources to report a positioning report.

WTRU Request for a Configuration Message or Resource

A WTRU may request the configuration message for positioning, e.g., whenin INACTIVE state. The WTRU may include such request as part of an RRCmessage (e.g., a standalone RRC resume request, or indicated as part ofa resume cause of an RRC resume request). The WTRU may include suchrequest as part of MsgA, part of Msg3, part of a context transfermessage, or part of the CG transmission. In one method, the WTRU mayinclude such request for positioning configuration and/or a resource forpositioning upon satisfying at least one of the following:

-   -   If the WTRU does not have a resource for transmitting a        positioning resource. For example, the WTRU may include such        request if it does not have a PUSCH grant or if an available CG        becomes no longer valid (e.g., due to mobility to a different        cell, expiry of the associated TA timer, and/or releasing the CG        configuration)    -   After mobility to a different serving cell or a different RNA        (e.g., a cell in a different RAN Notification Area (RNA) or        tracking area)    -   Upon expiry of a timer: For example, the WTRU may request a        resource for positioning if the TA timer associated with a CG        for reporting the position has expired or is about to expire. In        another example, the WTRU may start a timer upon reception of a        PUSCH resource (e.g., CG) for transmitting positioning reports.        The WTRU may transmit positioning reports while such timer is        running and may stop the reporting after timer expiry.

A WTRU may request a resource for transmission of the positioningreport, transmission of the SRSp, and/or transmission of a positioningrelated reference signal. Specifically, since such a need may not bereflected in a Buffer Status Report (BSR), an explicit indication may beused (e.g., an RRC message or an LPP message—e.g. configuration requestmessage—) to request the resource. The WTRU may want to transmit or maytrigger transmission of such a positioning measurement report when theWTRU does not have an UL resource to transmit it on, e.g., after apreceding transmission.

In one method, the WTRU may indicate such need for an uplink positioningresource as part of a BSR or as part of a small data BSR MAC CE. TheWTRU may be configured with a (Logical Channel (LCH), (Logical ChannelGroup) LCG, and/or a (Data Radio Bearer) DRB associated withtransmission of positioning report bits, which may be considered by theWTRU as small data. The WTRU may report that it has new small data(e.g., the positioning report) ready for transmission to the network aspart of a BSR or in a small data BSR MAC CE. The WTRU may trigger a newBSR (or small data BSR) upon generation of the new small data, or apositioning report for transmission. If the WTRU already has a validUL-SCH resource for the inclusion of the BSR MAC CE, the WTRU maymultiplex the BSR MAC CE on it. For example, the WTRU does not need totrigger a BSR for requesting UL resources for transmitting a positioningreport if it already has buffered data pending from other non-SDT DRBs.Rather, the WTRU can simply append the request for UL resources fortransmitting a positioning report onto the BSR that will be transmittedfor the already pending buffered data.

Furthermore, a WTRU may cancel an already pending small data BSR upon orafter at least one of the following: (1) inclusion of all small data inthe SDT resource, (2) upon/after inclusion of the SDT BSR MAC CE in aPDU, if there is no other small data buffered, (3) upon transmitting asubsequent small data transmission (transmission of another small datatransmission AFTER the transmission of the initial small data PDUcontaining the BSR MAC CE, possibly on a different SDT resource), (4) UEreceives a HARQ-ACK value equal to “ACK” for the PDU transmitted whichcontains the multiplexed BSR MAC CE, and/or (5) after receiving anuplink grant for a subsequent small data transmission. For instance, aWTRU may cancel an SDT BSR upon transitioning into connected mode (e.g.,including an RRC resume request or reception of an RRC connectionresumption/(re)-establishment message). The WTRU may trigger aScheduling Request (SR) in connected mode if it still has a pending SDTBSR or a positioning report to send. The WTRU may cancel the SDT BSR MACCE if it is a padding BSR, if there are no accompanied other data bitsin the PDU, and/or if there are data bits from non-SDT DRB(s) or LCH(s).The WTRU may initiate a new RACH procedure when an SDT BSR is triggeredand the WTRU does not have any valid UL-SCH resources for thetransmission of the SDT BSR. The WTRU may be configured with mappingrestrictions (e.g., LCP mapping restrictions or a type of UL-SCHresources on which the BSR can be transmitted), whereby the WTRU onlymultiplexes the SDT BSR on a resource if it meets the configured mappingrestrictions.

The WTRU may indicate the intention of transmitting SRSp in a small datatransmission prior to the SRSp. For example, the WTRU can indicate theintention of transmitting SRSp in MsgA, msg1, msg3, or part of a PUSCHtransmission. The WTRU may then transmit the SRSp on configuredresources. The WTRU may transmit the SRSp as part of the CG resourcesconfigured for small data transmission. The WTRU may multiplex SRS andother channels such as PUCCH or PUSCH in the CG resources configured forsmall data transmission.

Configurations

The WTRU in idle/inactive mode may receive either the PRS/SRSpconfigurations (for WTRU-based and WTRU-assisted positioning), therequest for positioning information (for WTRU assisted positioning), ormeasurement reports (for WTRU-based positioning), in one or more of thefollowing:

Connection establishment procedure: For example, a WTRU may be providedwith at least one SRSp (pre)configuration (e.g., via RRC signaling)and/or at least one PRS configuration (e.g., via RRC or LPP signalling)by the network based on the WTRU capability information either during orafter connection establishment or registration procedure. The WTRU mayreceive the PRS/SRSp configurations while in RRC connected state, forexample.

SIB/On-demand SIB: For example, the WTRU may directly receive thePRS/SRSp configurations in the SIB. In another example, a WTRU may betriggered to use a PRS/SRSp configuration based on the cell ID receivedin the SIB and the mapping between PRS/SRSp configurations and cell IDconfigured in the WTRU. For PRS, the WTRU may receive in the SIB anindication containing the identifier of a PRS configuration to beapplied/activated for making DL measurements while in idle/inactivemode, for example. For SRSp, the WTRU may receive in the SIB anindication containing the identifier of SRSp resources and otherparameters (e.g., periodicity) or the type of resources (e.g., RACH,Sounding Reference Signal (SRS)) to be used for transmitting SRSp in ULwhile in idle/inactive mode, for example. For UL-based positioning, theWTRU may also apply a pre-configured or an indicated selection criterion(e.g., listen-before-talk, random back-off) for mitigating interferencewhen transmitting SRSp, for example. In another example, the WTRU may betriggered to send an on-demand SIB message to the network for requestingPRS/SRSp configuration upon receiving a minimum SIB from the network(e.g., without the positioning configuration related information in thereceived SIB) and determining the accessibility of positioning SIB withon-demand SIB request, for example.

Paging (Core network and/or RAN paging): For example, the WTRU mayreceive the PRS/SRSp configuration upon receiving a CN or RAN pagingmessage during the on-duration of a DRX cycle in idle/inactive mode. Inthis case, the WTRU may set an inactivity timer with a particularconfigured time duration corresponding to the reception of PRS or SRSpconfiguration, for example. As an example, the duration for theinactivity timer for extending the on-duration may be set by theWTRU-based on the identifier/index included in the paging message (e.g.,different identifiers may be used for PRS or SRSp) or based on the typeof paging message (e.g., CN paging or RAN paging). In one example, theWTRU may receive an activation message for transmitting SRSp or themeasurement report for WTRU-based positioning in RAN paging messages. Inanother example, the WTRU may receive the request forlocation/positioning information from the LMF in a CN paging message. InRAN paging and/or CN paging messages, the WTRU may determine thecorresponding action (e.g., activation of SRSp transmission or measuringof DL PRS) either based on the identifier/index associated with theaction included in the RAN/CN paging messages or based on implicitsignaling sent in the paging messages (e.g., reception of a first pagingmessage followed by a second paging message within a certain timeduration).

Initial access messages: For example, the WTRU may receive either inMessage 2/4 (in 4-step RACH procedure) or in Message B (in 2-step RACHprocedure) one or more of the following:

-   -   PRS/SRSp configurations: For example, the WTRU may receive one        or more of the PRS/SRSp configuration parameters and/or the        PRS/SRSp identifiers (e.g., when receiving an indication        indicating the selection of a preconfigured PRS/SRSp)    -   PRS: For example, the WTRU may receive PRS from one or more TRPs        associated with a gNB that receives the triggering message        (e.g., Msg 1/3 or Msg A) from the WTRU    -   Request for location information (e.g., for WTRU-assisted        positioning)    -   Measurement report (e.g., for WTRU based positioning)

In the case when the WTRU determines that PRS/SRSp configurations areunavailable (e.g., when triggered by higher layers/network) or theexisting PRS/SRSp configurations are not applicable/valid, the WTRU maysend an indication to the network requesting PRS/SRSp (re)configuration.In addition to the request for PRS/SRSp, the WTRU may also transmit SRSpand other messages including measurement reports (e.g., for WTRUassisted positioning) in one or more of the following:

-   -   Initial access messages: For example, the WTRU may send the        request for PRS/SRSp either in Message 1/3 (in 4-step RACH        procedure) or in Message A (in 2-step RACH procedure)    -   SRSp resources: For example, the WTRU may send the measurement        report in the resources associated with SRSp for UL+DL based        positioning    -   TA/RNA (Tracking Area/RAN Notification Area) update messages    -   On demand SIB

The contents of the indication sent by the WTRU requesting for PRS/SRSpconfiguration may include one or more of the following information:

-   -   WTRU ID: For example, the WTRU may include the WTRU ID assigned        by the CN (e.g., Temporary Mobile Subscriber Identity (TMSI)) or        RAN (I-RNTI). In another example, the WTRU may include a random        ID selected from a pool of IDs configured/accessible to the        WTRU. In this case, the WTRU may select an ID from different ID        pools associated with different types of PRS/SRSp        configurations, for example.    -   PRS/SRSp ID    -   DRX configuration ID

An example of signaling flow is shown in FIG. 2 for 4-step RACH for DLpositioning methods for measurement report transmission during inactivemode. The WTRU 201 receives a PRS configuration 212 and Location Request216 from the gNB 203, which may be generated by the LMF 205 (e.g., see210 and 214). The WTRU 201 measures (220) a PRS (218) transmitted by thegNB 203 and returns a RACH Preamble in Msg 1 (222). An uplink grant issent to the WTRU 201 in Msg 2 (224). The measurement reportcorresponding to the received PRS is sent in Msg 3 (226). In thisexample, PRS is sent in Msg 4 (230). The measurement reports are sent tothe LMF from the gNB (228). If PRS is not configured by the network,RACH Preamble may be replaced by request for PRS configuration which mayinclude the WTRU ID, as described previously.

Another example of signaling flow is shown in FIG. 3 for 2-step RACH forDL positioning methods for measurement report transmission duringinactive mode. The WTRU 201 receives PRS configuration 312 and LocationRequest 316 from the gNB 203, which may be generated by the LMF (see 310and 314). The WTRU 201 measures (320) a PRS 318 transmitted by the gNB203 and returns RACH Preamble in Msg A (322), for example. An uplinkgrant 326 is sent to the WTRU 201 in Msg B 326. A measurement reportcorresponding to the received PRS is sent back to gNB in Msg A 328. Themeasurement reports are sent (330) to the LMF 205 from the gNB 203.

An example of signaling flow is shown in FIG. 4 for 4-step RACH for ULpositioning methods for measurement report transmission during inactivemode. The WTRU 201 receives RAN paging 422 to activate UL SRS, which maybe initiated by the LMF 205 (e.g., see 420). The WTRU 201 returns theRACH preamble 424. In return, the gNB 203 returns RAR in Msg 2 426. InMsg 3 428, the WTRU transmits SRS. The gNB 203 can then measure the SRSp(430) and transmit a measurement report 432 to the LMF 205

An example of signaling flow is shown in FIG. 5 for 2-step RACH for ULpositioning methods for measurement report transmission during inactivemode. Signals similar to those discussed in FIG. 4 are not discussed.The WTRU 203 receives RAN paging 522 to activate UL SRS. The WTRUtransmits SRSp in Msg A 524.

WTRU in Idle/Inactive Mode Sends Indication to Network for PRS/SRSp(Re)Configuration Based on Validity Tag

In one embodiment, a WTRU in inactive/idle mode may send an indicationto the network requesting (re)configuration of PRS/SRSp based on aconfigured validity tag. The WTRU may be initially configured with oneor more PRS and/or SRSp configurations, which may be maintained by theWTRU when operating in idle/inactive mode, for example. The differentPRS/SRSp (pre)configurations may be assigned with an identifier. Inaddition, the WTRU may also be configured with a positioning validitytag associated with the PRS/SRSp configurations, which may also bemaintained for the duration of the WTRU remaining in idle/inactive mode.The positioning validity tag may contain one or more of the followinginformation/conditions:

-   -   Time validity: For example, a time duration may be associated        with individual PRS and/or SRSp (pre)configurations in the WTRU.        In another example, a common time duration may be associated two        or more PRS/SRSp configurations in a group or all of the        PRS/SRSp (pre)configurations configured in the WTRU. The WTRU        may initialize a timer when transitioning to idle/inactive mode        and may use the PRS/SRSp configuration for positioning during        idle/inactive mode as long as the associated timer has not        expired, for example.    -   Area validity: For example, a validity area consisting of at        least one cell (e.g., determined by the Cell ID) may be        configured in the WTRU and associated with either an individual        PRS/SRSp (pre)configuration or a group of PRS/SRSp        (pre)configurations. The WTRU may be mobile within the one or        more cells in the validity areas and may be allowed to use the        PRS/SRSp (pre)configuration as long as the cell identifier        related information (e.g., list of cell IDs) matches the        information in the validity area, for example.    -   Allowed derivations: For example, the WTRU may be allowed to        derive/determine the PRS/SRSp configurations based on a        combination of two or more pre-configurations when satisfying        certain conditions (e.g., the RSRP measurement is above a        threshold, detection of multipath with/without LoS)

When triggered by a request for location information from the LMF (forWTRU-assisted positioning) or from higher layers/application in WTRU(for WTRU-based positioning), the WTRU may verify the conditions in thevalidity tag to determine if the (pre)configured PRS/SRSp is stillvalid. In this case, the WTRU may use the PRS/SRSp (pre)configurationsif the conditions in the validity tag are satisfied. In the case when atleast one of the conditions in the validity tag is not satisfied, theWTRU may send a request for reconfiguring the PRS/SRS configurations.The WTRU may receive the PRS/SRSp (re)configurations upon determiningthe expiry of the validity tag in one or more of the methods indicatedin the previous section, for example.

With the above methods, the WTRU may start the positioning processduring IDLE or INACTIVE mode, allowing the WTRU to reduce powerconsumption while achieving high accuracy in positioning.

Context Retrieval

Context retrieval may be possible if the following conditions aresatisfied. For an inactive state, the WTRU may persist or store the PRSand/or SRSp configuration as part of the WTRU context. Suchconfiguration may include the positioning resource for PRS and/or SRSp,the sequence ID used to determine the PRS, etc. The WTRU may assume theconfiguration is applicable for a subset of serving cells, e.g., servingcells for which the context is still known at the gNB, cells in the sameRNA, cells that do not require anchor relocation, etc.

WTRU Uses the Stored CG Configuration in WTRU Context while in RRCInactive/Idle Mode

In one embodiment, a WTRU in RRC Inactive/Idle mode uses the CGcontained in the WTRU context for sending positioning information and/ormeasurement reports to the network, e.g., using the configurationassociated with the CG received while in RRC Connected mode. The CGconfiguration received by the WTRU in RRC signaling (e.g., either Type 1or Type 2) may include one or more of the following: C-RNTIconfiguration, BWP configuration, periodicity, time domain offset, timedomain allocation, and number of HARQ processes. Additionally, the WTRUmay receive one or more identifiers and validity conditions associatedwith the CG configuration for using the CG for positioning whenoperating in RRC idle/inactive mode. For example, the WTRU in RRCidle/inactive mode may use the CG configuration if the associatedvalidity condition (e.g., validity time duration, TA timer, cell IDs inRNA) is satisfied. In another example, when one or more of the validityconditions is/are not satisfied or expire(s), the WTRU in RRCidle/inactive state may send a request, e.g., in a RRCResumeRequest, fora new CG configuration, and receive a new CG configuration, e.g., in anRRCRelease message. The WTRU may then send the positioning informationand/or measurement report to the network using the received new CGconfiguration while remaining in RRC idle/inactive state. Alternately,the WTRU may transition to RRC Connected state, upon receiving the newCG configuration, e.g., in a RRCResume message, and then send thepositioning information and/or measurement report to the network whilein CONNECTED state.

The WTRU may receive the CG configuration while operating in RRCConnected mode in dedicated RRC signaling messages. The WTRU also mayreceive the CG configuration in an RRCRelease message, under thesuspendConfig configuration (e.g., in Msg B or Msg4), for example. Inthis case, the CG configuration in the RRCRelease message may bereceived when transitioning to RRC Inactive mode from RRC Connected Modeor upon the WTRU sending an RRCResumeRequest while in RRC Inactivestate, for example.

In one example, the CG configuration received by the WTRU, e.g., in anRRCRelease message, may contain the same or a different configurationthan had been received by the WTRU while in RRC Connected state. In thiscase, the WTRU may receive the same or a different identifier associatedwith the CG configuration for use during RRC Inactive state. In anotherexample, the WTRU may receive a differential CG configuration in anRRCRelease message which may possibly contain at least in part someconfiguration information which is common with the CG configurationreceived/used during RRC Connected state. For example, the differentialCG configuration may include an increase/decrease in the number oftime/frequency resources and/or a change in the periodicity relative toa previous CG configuration received during RRC Connected mode. In suchcase, the WTRU may receive in an RRCRelease message the same identifierassociated with the previous CG configuration along with the deltaconfiguration information indicating the differential CG configuration,for example.

The WTRU may store the received CG configuration in the WTRU context andapply the stored configuration for sending one or more of the followingwhile in RRC Inactive/idle mode:

-   -   Location Service (LCS) client request to LMF for positioning        information (e.g. for Mobile Originated-Location Request (MO-LR)        service)    -   WTRU capability information (e.g., supported positioning        methods)    -   Request for assistance information (e.g., PRS/SRSp        configurations), including aperiodic or periodic requests for        assistance data    -   Positioning information, including estimated/calculated WTRU        location for WTRU-based positioning (e.g., for Mobile        Terminated-Location Request (MT-LR) service). The positioning        information may be sent to the LMF either aperiodically or        periodically, for example.    -   Measurement report (e.g., for LMF-based positioning), consisting        of measurements made on the received PRS, which may be sent        either aperiodically or periodically

In addition, the WTRU also may store spatial/QCL relationship of thePRS, such as TCI information, QCL-TypeA, QCL-TypeB, QCL-TypeC orQCL-TypeD, spatial relationship, with other RS or channelsreceived/determined while in RRC Connected mode to be used upontransitioning to RRC Inactive/Idle mode based on similar RRC signalingand/or validity conditions applied for using the CG configuration.

WTRU Uses a Positioning Method/Configuration during RRC Inactive/IdleMode that is Correlated with the Positioning Method/ConfigurationApplied during RRC Connected Mode

In one embodiment, the WTRU may use one or more positioning methods thatare applied while in RRC Connected mode for positioning when operatingin RRC Inactive/Idle mode. For example, the WTRU configured to support aDL-based or UL-based positioning (i.e., triggered to be performed eitheras WTRU-based or LMF-based positioning), may use the same positioningmethod configured during RRC Connected state after transitioning to RRCInactive/Idle state. In another example, the WTRU may use a positioningmethod upon transitioning to RRC Inactive/Idle mode, which may bedifferent than the method used during RRC Connected state. In bothexamples, the one or more configurations associated with the positioningmethods (e.g., PRS/SRSp configurations) that are applied by the WTRU inRRC Inactive/Idle mode may be either the same or different than theconfigurations applied while in RRC Connected mode.

The WTRU may receive from the network while in RRC Connected mode (e.g.,just or prior to transitioning to RRC Inactive/Idle mode) an indicationof whether to use the same or a different positioning method and/or theassociated configuration when it is in Inactive/Idle mode. For example,the WTRU may receive an explicit indication, e.g., in an RRCReleasemessage, the indication on whether to retain or release the one or morepositioning methods and/or the associated configurations that it hadbeen using while in RRC Connected mode. In this case, the RRCReleasemessage may contain the identifiers of the positioningmethod/configurations to be retained and/or released when operating inRRC Inactive/Idle state. In another example, the WTRU may receive animplicit indication to retain the positioning method(s) either (a) basedon an absence of any indication indicating that it should release thepositioning method(s) or (b) when the same positioningmethod/configuration is continued to be used by the network (e.g.,DL-PRS transmission) after the WTRU transitions to RRC Inactive/Idlemode. Alternatively, the WTRU may receive an implicit indication tochange the positioning method(s) as a function of changes of the report,such as removal or addition of specific measurements. Examples ofmeasurements include:

-   -   angles of arrival,    -   time difference of arrival,    -   reference signal time difference,    -   time of arrival,    -   RSRP of PRS or reference signals used for positioning,    -   WTRU Rx-Tx time difference,    -   Time stamp of measurement,    -   Quality for each measurement, and/or    -   Number of paths.

With the above methods, the WTRU can start the positioning processduring IDLE or INACTIVE mode, allowing the WTRU to reduce powerconsumption while achieving high accuracy in positioning.

RACH Procedure for Positioning Msq A,B Including Variations forIDLE/INACTIVE

The WTRU may perform positioning measurements and report them in part ofMsg3/A, a grant scheduled by the gNB and provided part of MsgB or Msg4,a grant scheduled by the gNB after the completion of the RACH procedure(e.g., Msg 5), and/or an uplink configured grant.

The WTRU may remain in IDLE or inactive mode after reporting apositioning related measurement and/or report in a RACH procedure. For aRACH procedure initiated in IDLE or inactive mode for positioning, theWTRU may include a specific RRC message in Msg3 or MsgA to indicate tothe gNB the intention that this RACH procedure is performed to reportpositioning data or to obtain positioning related configuration(s). TheWTRU may select a PRACH (Physical Random Access Channel) resource (apreamble group and/or PRACH occasion) to indicate to the network thatthis RACH (Random Access Channel) procedure is for positioning, toreport positioning data, and/or to obtain positioning relatedconfiguration(s).

The WTRU may discard a C-RNTI (Cell-RNTI) or a temporary C-RNTI obtainedas part of a RACH procedure in IDLE mode for positioning, e.g., uponsuccessfully reporting the WTRU position or the positioning relatedreport and/or going back to DRX sleep. The WTRU may monitor a PDCCH(Physical Downlink Control Channel) addressed to such C-RNTI, possiblyfor a period of time, e.g., until successfully performing allpositioning-related transmissions and/or transmitting a relevant WTRUpositioning or positioning report.

PRACH Partitioning

The WTRU may provide SRSp as part of the PRACH procedure, or indicate tothe gNB that it will transmit SRSp as part of the RACH procedure, e.g.,where such indication can be performed by the WTRU by selecting a subsetof PRACH resources (e.g., preambles and/or RACH occasions which can bepreconfigured to indicate to the gNB that the WTRU is using such RACHfor positioning and/or transmitting SRSp part of the RACH procedure). Inone example, the WTRU may transmit the SRSp as part of the PUSCHtransmission (e.g., by puncturing the PUSCH transmission, by appendingit, or at the end of it) associated with the RACH procedure or aconfigured grant.

Association between RACH Resource (i.e., RACH Occasion+PreambleCombination) and PRS or SRSp

The WTRU may use message 3 or message A to transmit measurement reportsto the network. The WTRU may be configured with the following set ofassociations to determine the PRS resource that the WTRU receives.

In one embodiment, the WTRU may receive two sets of associations. In thefirst set of associations, each SSB may be associated with a RACHOccasion (RO). Alternatively, multiple SSBs may be associated with oneRO or multiple ROs can be associated with one SSB. In the second set ofassociations, information regarding spatial relation or QCL relationshipbetween the SSB and other reference signals, such as PRS, or channelsmay be included. Examples of different types of QCL can be found in 3GPPTechnical Specification 38.214.

The WTRU may receive the second set of associations via broadcast fromthe network. The WTRU may determine the spatial filter to use to receivePRS resources in message 4 or message B according to the first andsecond sets of associations. Alternatively, the WTRU may receive the PRSconfiguration during message 2 or message B from the network. The WTRUmay, for example, be configured to receive the PRS in any one or more ofthe following locations:

-   -   PRS resource in message 4    -   PRS resource in message B    -   PRS resource outside of message 4 or message

With the above methods, the WTRU can send the measurement reports to theserver during IDLE or INACTIVE mode, allowing the WTRU to reduce powerconsumption while achieving high accuracy in positioning.

Transition to RRC_CONNECTED

The WTRU may include an indication of preference to transition intoconnected mode. Such indication can be transmitted by including an RRC(re)-establishment request, an RRC resume request, an RRC message toindicate preference to transition to connected mode, and/or anindication part of the payload, the MAC subheader, or a MAC CE. Theindication can be provided as part of MsgA, as part of Msg3, as part ofMsg1 (e.g., by preamble selection), on a CG, or on a scheduled grantprovided for subsequent transmission.

The WTRU may include such indication of preference to transition intoconnected mode in response to one or more conditions. In one method, theWTRU may issue the indication if: the WTRU does not have valid securitykeys to transmit the payload, the payload of the positioning report islarger than a certain threshold, the reporting resource in idle orinactive state does not meet the required latency to provide thepositioning report, more accurate positioning measurements are needed,the size of the payload is above a threshold, and/or more granularpositioning data/report is required. In one example, the WTRU may issuethe indication to transition to connected mode if the RACH—or ConfiguredGrant (CG) periodicity for reporting the positioning report is largerthan a threshold. The WTRU may provide the indication to transition toconnected mode if the number or size of measurement reports, which aregenerated by the WTRU after PRS is received by the WTRU, is above athreshold, if the number of measured cells is above a threshold, and/orif the report size is larger than the size of the PUSCH resourceassociated with the RACH procedure of the CG.

The WTRU also may provide such indication after a configured orpredetermined number of failed attempts to transmit the positioningreport/data. The WTRU may also provide such indication after the expiryof a configured or predetermined timer. The WTRU may start such timerupon the first transmission attempt of a positioning report, and maystop the timer upon successfully transmitting a positioning report(e.g., receiving a HARQ-ACK or receiving a DL RACH message following thetransmission that echoes Msg3 or MsgA).

With the above methods, the WTRU is able to send the measurement reportsto the serve in order to achieve high positioning accuracy, whileallowing the WTRU to reduce power consumption.

Security Handling for Positioning During IDLE Mode

Security Retrieval during IDLE Mode for PositioningReporting Data in IDLE when Security Keys have been Discarded

A WTRU may use a subset of positioning methods (e.g., uplink-basedpositioning, WTRU-assisted positioning, or WTRU-based positioning) inIDLE mode. In one method, the WTRU may restrict the positioning methodto uplink-based positioning (based on SRSp transmission) in IDLE mode,e.g., when the security keys are not available. In another method, theWTRU may be provided with a temporary security key as part of the RACHprocedure (e.g., including MAC-I, possibly as part of an RRC message) totransmit the WTRU position or a positioning report (associated withWTRU-assisted DL based positioning). Such temporary security key may beassumed valid by the WTRU for a certain period (pre-configured orindicated) or for a limited number of UL grant(s) provided after Msg2,Msg4, or MsgB.

In one method, the WTRU may initiate a new RACH procedure forpositioning using an RRC message (e.g., RRC resume or RRCreestablishment) if the security keys are no longer valid. The WTRU mayassume security keys to be valid in the same set of serving cell(s) forwhich the WTRU context is known (e.g., the same serving cell beforetransitioning into inactive state from connected state, and/or any othercell in the same RNA. The WTRU may use a CG resource only if thesecurity key is maintained and known at the serving cell (e.g., ininactive state for the same serving cell or another cell in the sameRNA).

In one embodiment, a WTRU in idle mode determines the security keys tobe used for encrypting and sending the positioning related messages tothe network. For WTRU-based positioning in idle mode, the WTRU may senda request for PRS configurations to the LMF and receive the PRSconfigurations in encrypted NAS messages. Likewise, for WTRU-assistedpositioning in idle mode, the WTRU may receive the PRS configurationsand request positioning information from the LMF, and sends measurementreports in encrypted NAS messages to LMF.

For determining the security keys to be applied when sending/receivingpositioning related messages in idle mode, the WTRU may perform one ormore of the following actions:

-   -   Reuse the CN provided security keys: For example, the WTRU may        use the security keys along with the CN-provided WTRU identifier        (e.g., TMSI (Temporary Mobile Subscriber Identity), IMSI        (International Mobile Subscriber Identity)), which may be        received during initial access and applied in RRC connected        mode. The security keys may be associated with time/area        restrictions which the WTRU may monitor prior to using the keys        during idle mode, for example    -   Derive security keys: For example, the WTRU may derive the        security keys to be applied for transmitting/receiving NAS        messages in idle mode using a configured key derivation        algorithm and the CN provided WTRU identifier. The WTRU may also        be configured to include positioning related identifiers (e.g.,        PRS configuration ID) for deriving the security keys.    -   Select security keys from pre-configurations: For example, the        WTRU may select one set of security keys from multiple        pre-configurations based on selection criteria (e.g., based on        timer and/or cell IDs in Tracking Area) which may be configured        by the network in the WTRU prior to transitioning into idle        mode.    -   Retrieve security keys: For example, the WTRU may send an        indication to the network containing the CN-provided WTRU        identifier (e.g., in Msg A/Msg 1) while moving within the        Tracking Area in order to retrieve security keys and/or initiate        a security key derivation procedure. The WTRU may send the        indication to the network upon determining the expiry or        inaccessibility of the stored security keys, for example.

With the above methods, the WTRU is able to send the measurement reportsto the server securely during IDLE or INACTIVE mode, allowing the WTRUto reduce power consumption while achieving high accuracy inpositioning.

WTRU Behavior during Measurement Reporting Resource Allocation ResourceRetrieval for Reporting Positioning Data

If available, the WTRU may use PUSCH resources associated with aconfigured grant in inactive state if the WTRU context is known by theserving gNB, and/or uplink timing is maintained (e.g., TA (TimingAdvance) value is either zero or is maintained by a timing alignmenttimer). The WTRU may assume the CG is useable, even if it moves to aserving cell other than the one from which it received the CGconfiguration if that cell is part of the same RNA or Tracking Area.Otherwise, the WTRU may initiate a RACH procedure and use PRACHresources to report positioning data.

Sizing, Segmentation, and Optimization of Reporting Contents

During IDLE or INACTIVE mode, bandwidth for the uplink transmission maybe limited and the grant size may not be large enough to contain themeasurement report that the WTRU generates.

Positioning Measurement Payload Indication

A WTRU may determine a payload size of the measurement. The payload sizeof positioning measurement reporting may be determined based on one ormore of the following:

-   -   The number of PRS configurations associated with the reporting    -   The number of positioning measurements that meet the applicable        requirements (e.g., the positioning measurement quality)    -   The number of TRPs or cells associated with the positioning        measurement    -   The number of positioning measurement methods used    -   The number of beams used for the positioning measurement    -   The number of positioning measurement results which have a LoS        path in its measurement    -   The number of LoS paths or additionally detected paths to        report,    -   TRP ID, cell ID, global cell ID, or unique ID associated with        the WTRU    -   Timing related information such as RSTD associated with pairs of        received PRSs or WTRU RX-TX time differences associated with the        number PRSs the WTRU receives    -   The number of Rx-Tx time differences to report    -   The number of RSRP values associated with paths or pairs of PRS        or WTRU RX-TX time differences

In one embodiment, a WTRU may indicate its payload size for thepositioning measurement reporting to receive an uplink grant sufficientto carry the positioning measurement reporting. One or more of followingmay apply:

-   -   PRACH resource partitioning may be used. For example, PRACH        resources dedicated for the aperiodic positioning measurement        reporting may be configured and a subset of the PRACH resources        may be associated with one or more payload sizes for the        positioning measurement reporting        -   Each subset of the PRACH resources may be associated with a            range of payload sizes        -   In one embodiment, a WTRU is only allowed to use a PRACH            resource that is associated with a payload size equal to or            larger than its payload size to be reported        -   When contention-based RACH is used, a WTRU may determine one            of PRACH resource partitions, wherein each PRACH resource            partition may be associated with a payload size (or range of            payload size). For example, a first partition may support a            first range of payload size (e.g., <100 bytes), a second            partition may support a second range of payload size (e.g.,            100-500 bytes), a third partition may support a third range            of payload size (e.g., 500-1000 bytes), and so on. When the            payload size determined for the WTRU is in the first range            of payload size, the WTRU may start to use (or may be            required to use) a PRACH resource in a first partition. If            the WTRU fails to receive RAR for the previously transmitted            PRACH, the WTRU may use (or may be allowed to use) a next            partition (or a partition that can support the determined            payload size). Herein, the partition may be interchangeably            used with PRACH resource partition    -   When 2-step RACH is used for positioning measurement reporting,        RACH MsgA partitioning may be used based on the payload size.        For example, RACH MsgA resources dedicated for the aperiodic        positioning measurement reporting may be configured and a subset        of the RACH MsgA resources may be associated with a payload size        (or range of payload sizes)        -   A RACH MsgA resource associated with a smaller payload size            may use, correspond to, or determine a PUSCH resource that            may have a smaller number of RBs (Resource Blocks) as            compared with that for a RACH MsgA resource associated with            a larger payload size    -   The payload size may be explicitly indicated during a RACH        procedure. For example, a WTRU may indicate its payload size for        positioning measurement reporting in MsgA/Msg3 during the RACH        procedure. The WTRU may receive a PUSCH resource allocation        after RACH procedure is finished

Subsequent Transmission

In one embodiment, the WTRU may include an indication for subsequenttransmission (e.g., part of MsgA, Msg3, or a CG PUSCH resource), whenthe positioning report or the WTRU's position does not fit into thePUSCH grant (as a result of the Logical Channel Priority (LCP)procedure). The WTRU may monitor a PDCCH addressed to C-RNTI or I-RNTIfor the reception of a PUSCH resource to perform a subsequenttransmission.

The WTRU may select a PRACH resource (a preamble group and/or PRACHoccasion) as a function of the payload size required to deliver thepositioning report. The WTRU may be configured by RRC or provided bybroadcast signaling with a mapping between a subset of PRACH resource(s)and a payload size (or a size threshold).

The WTRU may segment a positioning report/data if it does not fit in anapplicable reporting PUSCH resource (as a result of LCP). The WTRU mayinclude a WTRU identity or the resource identity along with the report(e.g., I-RNTI, temporary C-RNTI, C-RNTI, and/or MsgB/RA-RNTI) for eachreport segment, which can help the network schedule a subsequenttransmission and/or identity the report segments and attach themtogether. In IDLE mode, the WTRU may select the same RACH resource(e.g., RACH Occasion (RO)) to transmit a subsequent segment of apositioning report. This would allow the gNB to potentially put thesegments together by associating them with the RA-RNTI. In IDLE mode, ifthe WTRU remains in IDLE mode yet has subsequent segments to transmit,the WTRU may include its identity (or the resource identity used for thefirst segment part of the payload) in each subsequent segment. The WTRUmay include an indication that the PUSCH payload is segmented or thatmore segments are remaining for transmission (e.g., in a MAC subheader).Such indication may be considered by the network to be an implicitrequest for subsequent transmission indication.

Segmentation/Apportionment Methods

In one method, the WTRU may determine segmentation and/or apportionmentand reporting methods for the content of the report based onconfigurations. The configurations may include at least one of thefollowing:

-   -   The WTRU is not configured with segmentation. In this case, the        WTRU determines at least one of the following reporting methods:        -   The WTRU reports only a portion of the available relevant            data (that can fit within the available resources). In one            embodiment, the WTRU may not report received power related            information or timing related information for additional            paths. The WTRU only reports RSTD per pair of the PRSs that            the WTRU receives or WTRU RxTx time difference per received            PRS the WTRU receives. The WTRU may report RSRP of PRSs that            the WTRU receives.        -   o The WTRU autonomously decides the content of the report            based on the payload size.    -   The WTRU is configured with a number of segments and the WTRU        determines to partition the measurement report according to        predefined segmentation rules. The segmentation schemes may        include (1) segmentation schemes in which the measurement data        is split into subsets and all of it is transmitted to the        network and (2) segmentation schemes in which only some of the        segments are transmitted. The segmentation rules can include at        least one of the following rules:        -   Overhead only: The WTRU may determine to include information            related to the source of transmission of the PRS or            generation of the PRS, such as cell ID from which the PRS            was transmitted, global cell ID, or the ID used to generate            the PRS in one of the segments of the report        -   Timing and power information for the main path only: The            WTRU may determine to include the preconfigured amount of            information in one of the segments of the measurement            report, such as RSTD per pair of the PRSs that the WTRU            receives or WTRU Rx-Tx time difference per received PRS. The            WTRU may be configured to include power related information.        -   Timing information for the additional paths: The WTRU may            determine to include timing related information of            additional detected paths that are associated with each RSTD            per pair of the PRSs that the WTRU receives or WTRU Rx-Tx            time difference per received PRS. The WTRU may be configured            to include power related information of the PRSs that the            WTRU receives.        -   Timing information only: The WTRU may determine to include            timing related information, such as RSTD or WTRU Rx-TX time            difference for PRSs that the WTRU receives, and also timing            related information of additional detected paths associated            with each RSTD or WTRU Rx-Tx timing difference        -   Power information only: The WTRU may determine to include            power related information, such as RSRP for PRSs that the            WTRU receives, and also power related information, such as            RSRP or differential power compared to the reference PRS            associated with each RSTD or WTRU Rx Tx timing difference        -   Segment by TRP/Cell: The WTRU may determine to include            timing or power related information related to the origin of            the PRS transmission, such as TRP or cell from which the PRS            is transmitted. Therefore, the WTRU may segment the report            based on TRP ID or Cell ID or Global Cell ID.        -   Segment by positioning frequency layer: The WTRU may            determine to include timing or power related information            related to the PRS by positioning frequency layers.            Therefore, the WTRU may segment the report based on the            positioning frequency layer parameter.        -   Segment by PRS resource ID: The WTRU may segment the report            based on the PRS resource ID. For example, for the DL and UL            positioning method or DL angle of departure-based            positioning method, the WTRU measures timing or power            related information per PRS. Thus, the WTRU may segment the            report based on the PRS resource ID.

Power related information may include RSRP or differential powercompared to a reference RSRP, which may be the RSRP of the referencePRS. In this disclosure, PRS, PRS beam, and PRS resources may be usedinterchangeably. Similarly, in this disclosure, SRSp, SRSp beam, andSRSp resources may be used interchangeably.

In another embodiment, the WTRU may be configured with the number ofsegments to use for reporting. The WTRU may receive this configurationduring Msg A or Msg 2 or Msg 4 during the RACH procedure, or by pagingor broadcast.

Reporting Method for Segmented Report

The WTRU may assign the same identification number to each segment ofthe segmented report and send them to the network accordingly.Alternatively, the WTRU may assign a different identification number toeach segment of the segmented report and send them to the networkaccordingly. The WTRU may send a segmented report periodically or in apredetermined sequence. For example, the segment of the report thatcontains the overhead information (such as cell ID or TRP ID thatindicates the origin of the PRS) may not need to be sent on everyoccasion. Therefore, the WTRU may be configured with a measurementreport period during which the WTRU sends the segment containingoverhead information only once. For example, if the WTRU segments thereport into four segments, with identification numbers #0, #1, #2 and#3, where #0 contains the overhead information while other segmentscontain measurement reports, the WTRU may send #0 once during thereporting period, and send #1, #2 and #3 periodically. Each segment maycontain a common report ID such that the network can combine thesegmented reports together. As explained earlier, the WTRU may include aWTRU identity or the resource identity along with the report (e.g.,I-RNTI, temporary C-RNTI, C-RNTI, and/or MsgB/RA-RNTI) for each reportsegment.

In one method, the WTRU may periodically send the report. For example,if the WTRU segments the report into four segments, with identificationnumbers #0, #1, #2 and #3, where #0 contains the overhead informationwhile the other segments contain measurement reports, the WTRU may sendthe segmented report in the following sequence, #0, #1, #2, #3, #1, #2,#3, #1, #2, #3, . . . The WTRU may be configured with a segmentationreport cycling pattern. In addition, segments may be reported repeatedlyand the WTRU may be configured with the number of repetitions persegment of the report. For example, if the WTRU is configured with thenumber of repetitions K=2, the WTRU may send the segmented reports asfollows: #0, #1, #1, #2, #2, #3, #3, #1, #1, . . .

In one method, the WTRU may update the measurements contained in thereport. For instance, the WTRU may indicate to the network that thecontent of the report is updated by updating a flag associated with themeasurement report or segment that indicates that the measurementscontained in the segment is updated. The WTRU may send theaforementioned flag in MsgA, Msg3, or a CG PUSCH resource.

Procedure when Segmenting LPP Messages

When the payload size of LPP messages (e.g., LPPProvideLocationInformation) generated by a WTRU is relatively small, theWTRU may continue to perform measurements and send the LPP messageswhile remaining in INACTIVE state. However, it may be possible that theconfigured data volume threshold when supporting SDT is restricted, orthe allocated resource grant during INACTIVE mode may not be largeenough to carry the generated LPP message (e.g., measurement report).

For transmitting larger payload sizes, the WTRU may segment and send themeasurement reports/location estimates sequentially using resourcesconfigured for SDT with proper identifiers such that the receivedsegments of LPP messages/PDUs can be assembled either at the RAN or theLMF.

The number of segments supported may be determined by the WTRU either onits own or with LMF/gNB assistance based on one or more positioning QoSrequirements (e.g., accuracy, latency) and the configured data volumethreshold for SDT, for example. Upon segmentation, the WTRU may send thedifferent segments sequentially using SDT such that the overallpositioning information may be sent within the accuracy/latencyrequirement while adhering to the data volume threshold for eachsegment.

For supporting transmission of segmented LPP messages (e.g., containingmeasurement reports), the WTRU may receive from the network (e.g., theLMF and/or the RAN) certain segmentation configuration information suchas indications (e.g., identifiers, one or more flags to indicatesegmentation, end-markers), and/or sequence numbers (e.g., in headers)to use when segmenting the LPP messages/PDUs. Such configurationinformation may be received by the WTRU in assistance data (LPPProvideAssistanceData) or in a location request message (LPPRequestLocationInformation). The WTRU may then apply the segmentationconfiguration for segmenting and transmitting to the network thesegmented LPP messages/PDUs over multiple SDT transmission occasionswhen the generated LPP messages do not fit within the data volumethreshold.

Condition Based Reporting

Conditions that Trigger a WTRU to Report, e.g., the WTRU Observing aDifference in Measurements

A WTRU may monitor a trigger signal from a gNB, which may be a part ofpaging occasions, for example. The trigger signal may be, for example,the paging config itself, a paging message addressed to the WTRU's RNTI,a PDCCH, a DL RS, or a DL transmission on a subset of DL resources.

WTRU Autonomous Triggering of Positioning in IDLE/INACTIVE PeriodicReporting

In one approach, the WTRU may be configured to perform positioningreporting (e.g., positioning measurement for WTRU-assisted positioningtechnique and/or the positioning information for WTRU-based positioningtechnique) periodically. For example, the WTRU may use one or multipleCGs to report the positioning measurement and/or positioninginformation. Alternatively, the WTRU may use the configured RACHresources (MsgA, Msg3, and/or Msg5) to perform positioning reporting.

Event-Triggered Reporting

In another approach, the WTRU may perform positioning reporting based onone or any combination of the following positioning-related events

-   -   The WTRU detects a change in its position.    -   The WTRU detects a change in the measurements. Specifically, the        WTRU may perform measurement reporting if it detects a change in        the positioning measurements.        -   The change may be based on any of the following.            -   The WTRU detect a change in RSTD of the same pair of                TRPs between two PRS reception instances            -   The RSRP of the PRS becomes greater than and/or smaller                than a threshold and/or the RSRP difference between two                PRS reception instances from the same TRP is greater                than a threshold.            -   The WTRU detects an increase or decrease in the number                of paths (possibly the paths with RSRP being greater                than a threshold) and/or the WTRU detects a change in                the time gap between two paths of two different PRS                receptions from a TRP            -   The WTRU detects a change in RTT (time gap between SRSp                transmission and PRS reception).            -   Change in the WTRU's speed.

The WTRU may receive the configuration of even-triggered reporting(e.g., RSRP thresholds) along with the reception of the PRS/SRSpconfiguration (e.g., in the paging message, SIB, and/or RRC message whenthe WTRU is in the RRC connected state).

WTRU Performs Delta Reporting

In one approach, the WTRU may perform delta reporting for positioningreporting (e.g., reporting only the difference value of the givenparameter relative to a previously reported value for that sameparameter). Specifically, the WTRU may include the changed informationin the reporting. For example, the WTRU may be required to report RSTDsof multiple TRP pairs. However, the WTRU may include the changed RSTDsof the TRP pairs in the reporting. This approach may be motivated toreduce the size of the message.

In an embodiment, the WTRU may perform regular reporting in the periodicreporting and delta reporting in the event-triggered reporting. Thedelta reporting of an even-triggered reporting may be associated withthe last periodic reporting. Specifically, if the WTRU detects a changein the positioning measurement compared to the last periodic reporting,the WTRU may perform event-trigger reporting and/or the WTRU may includeonly the delta information compared to the last periodic reporting.

In an embodiment, the UE may determine which positioning measurementreport to perform based on the time-frequency resource of the configuredgrant and/or the size of each measurement report. For instance, the UEmay determine to perform a normal measurement report if the configuredgrant is sufficient for such reporting. Alternatively, the UE mayperform delta reporting if the configured grant is insufficient for afull report. Alternatively, the UE may perform delta reporting whilealso indicating the necessity of an additional report (e.g., fullreport) in the first grant. Such indication may be conveyed by a MAC CE(e.g., BSR) and/or a MAC header. In another embodiment, the UE maysegment the positioning measurement report into multiple sequentialreports. The UE may also indicate the necessity of a subsequent reportin the preceding report (e.g., in in the MAC CE and/or MAC header of thepreceding report).

Configured Grant Approach Configured Grant Allocation for MeasurementReporting

Upon triggering positioning measurement or reporting in IDLE or inactivestate, the WTRU may report its positioning measurement, its position,and/or positioning report (or related data) on preconfigured uplinkresources (e.g., a configured grant). The WTRU may use such resource ifthe Timing Advance is known or if a related timing alignment timer isstill running.

In another method, the WTRU may use uplink-based positioning regardlessof whether uplink timing maintenance is applied or not. An example oftiming maintenance is use of Timing Advance. For example, the WTRU mayuse uplink based positioning if: (1) a Timing Advance timing timer isrunning, (2) when a Timing Advance timer associated with a PUSCH orPRACH resource is running, if the RSRP associated with an associatedPUSCH resource or a PRACH resource is above a threshold, (3) if the RSRPassociated with small data transmission is above a threshold, and/or (4)if a Timing Advance value has been obtained since transitioning intoidle or inactive state.

For positioning report/data transmitted on CG resources, the WTRU maymonitor the PDCCH for HARQ-ACK determination after the transmission;such PDCCH may be scrambled by I-RNTI, C-RNTI, small data-RNTI, orCS-RNTI. The WTRU may monitor for an explicit HARQ ACK/NACK signalingand or assume HARQ-ACK to be ACK—or NACK—upon expiry of a configured orpredetermined timer. The WTRU may start such timer upon transmission ofthe payload on the CG resource. The WTRU may retransmit—or autonomouslyretransmit—the payload if the timer expires (1) before the WTRUreceives—or determines—a HARQ-ACK and/or (2) the WTRU receives a dynamicgrant for retransmission. Alternatively, the WTRU may flush the HARQbuffer associated with the payload upon timer expiry. In onerealization, such timer can be the legacy configured grant timer.

In one method, the WTRU may be configured with one or more TA timers.Each TA timer may be associated with one or more configured grants. Inone example, the WTRU may be configured with one TA timer associatedwith all configured grants in the idle/inactive mode for the WTRU. Inanother example, the WTRU may be configured with multiple configuredgrants wherein each configured grant is associated with one TA timer.

Upon the expiry of the TA timer associated with a configured grant, theWTRU may perform a RACH procedure to continue the positioningmeasurement reporting procedure. In one embodiment, the WTRU may reportthe positioning measurement in the RACH resource (e.g., MsgA for 2-stepRACH or Msg3 for 4-step RACH). In another embodiment, the WTRU mayreport the buffer status in the RACH resource upon the expiry of the TAtimer. Specifically, the WTRU may determine to include a BSR in MsgAand/or Msg3 to indicate the availability of the positioning measurementdata. In another approach, the WTRU may perform a RACH procedure toindicate the invalidity of the configured grant. Specifically, the WTRUmay be configured with a dedicated RACH resource (e.g., dedicated RACHpreambles or dedicated ROs) to report the invalidity of the configuredgrant (e.g., due to the expiry of the TA timer). The WTRU may then waitfor the command from the network to continue the positioning measurementreporting. The WTRU may then validate the configured grant by restartthe TA timer upon the reception of the timing advance command from thenetwork. Such command may be received in MsgA, Msg3, PDCCH, and/orPDSCH.

The WTRU may monitor one or more CORSETs/search spaces associated withone or more configured grants in the idle/inactive mode to receivecommand from the network after one or multiple uplink transmissions. TheWTRU may restart a TA timer associated with the configured grant basedon any one or more of the following commands from the network:

-   -   The WTRU successfully decodes a PDCCH from the network    -   The WTRU detects no PDCCH transmission in the configured        CORSET/search space (the WTRU may assume that the network        successfully receives the PUSCH(s) from the network with the        correct TA value)

In one method, the WTRU may be configured with a CG dedicated forpositioning measurement reporting. Specifically, the WTRU may beconfigured with one DRB/SRB (Signaling Radio Bearer), LCH, and/or LCGassociated with positioning measurement reporting. During the LCPprocedure, the WTRU may be restricted to multiplex the data of thehigher priority with the positioning measurement reporting data in theconfigured grant. Alternatively, the WTRU may be restricted to multiplexthe positioning measurement reporting data in the configured grant. TheWTRU may perform a RACH procedure to transmit other data and/or it mayuse other configured grants to transmit the other data.

In one method, the WTRU may be configured with a grant associated withthe DRX/DTX cycle configured for the WTRU in the idle/inactive mode. Inone approach, the WTRU may then be configured to monitor aCORESET/search space, which may occur before each set of one or moreresources of the following:

-   -   DL-PRS reception    -   UL-SRS transmission    -   PUSCH/PUCCH transmissions.

The WTRU may determine whether to wake up to perform DL-PRS reception,UL-SRS transmission, and/or PUSCH/PUCCH transmissions (e.g., to performpositioning measurement reporting) based on the availability of thePDCCH and/or the content of the PDCCH. For example, the WTRU may beconfigured by the network to wake up based on the PDCCH decoding statusin the configured CORESET/search space associated with the resources forDL-PRS reception, UL-SRS transmission and/or PUSCH/PUCCH transmission.In one configuration, the WTRU may be configured to wake up if there isno PDCCH decoded in the configured CORESET/search space. Otherwise, ifthe WTRU decodes a PDCCH, the WTRU determines whether the WTRU wakes upor not depending on the content of the bitfield in PDCCH. In anotherconfiguration, the WTRU may be configured not to wake up if it does notdetect a PDCCH in the configured CORESET/search space.

In another method, the WTRU may be configured to associate oneconfigured grant with a periodic/semi-persistent UL-SRS/DL-PRSmeasurement resource. The WTRU may then determine whether to performtransmission in the configured grant based on the reception/transmissionactivity of the associated resource. In one example, if there is noDL-PRS detected in a resource, the WTRU may determine not to performpositioning measurement reporting in the associated configured grant. Inanother example, the WTRU may not perform measurement reporting in aconfigured resource if it did not transmit UL-PRS in the associatedresource.

Timing for the WTRU to Expect Reception of PRS

In an embodiment, the WTRU may be configured to expect to receive thePRS a (pre)configured time offset after the reception of the timer forthe CG. The timer may expire, and the WTRU may need to perform the RACHprocedure to reset the timer. In that case, as soon as a new timer or anew value for the timer or the timer is reset for the CG, the WTRU mayexpect to receive PRS at the (pre)configured time offset.

Aperiodic Measurement Reporting Aperiodic Positioning MeasurementReporting

A WTRU may be triggered to report positioning measurement or to transmitSRSp when the WTRU is in idle/inactive mode. One or more of thefollowing features may apply:

-   -   One or more aperiodic PRS configurations may be configured,        determined, or used, and a subset of those aperiodic PRS        configurations may be indicated for the positioning measurement        reporting        -   The time/frequency location of the subset of aperiodic PRS            configurations for the measurement may be indicated in the            triggering message (or indication)    -   If a WTRU is in Idle/Inactive mode, the triggering message (or        indication) may include one or more uplink resources to use for        the reporting        -   The uplink resources may be one or more uplink resources in            the physical cells associated with the reporting. For            example, when paging is used to trigger the aperiodic            positioning measurement reporting trigger, the physical            cells associated with the reporting may be the physical            cells in the paging Tracking Areas            -   An uplink resource for each physical cell for the                physical cells in the paging Tracking Area may be                provided, wherein each physical cell may be associated                with a unique physical cell identity        -   The uplink resource may be one or more SRSp resources for            the WTRU to send        -   The uplink resource may be a set of PRACH resources for the            WTRU to use for content-free RACH procedure for the            positioning measurement reporting        -   The uplink resource may be a PUSCH resource which may be            scheduled in the DCI triggering aperiodic positioning            measurement reporting    -   When a WTRU is triggered to report positioning measurements, the        WTRU may determine the reporting based on the positioning        measurement quality. For example, if the positioning measurement        quality is below a threshold, the WTRU may drop the positioning        measurement reporting; otherwise, the WTRU may report the        triggered or requested positioning measurement

In an embodiment, a paging event may be used as the trigger for thepositioning measurement reporting, wherein a subset of paging occasions(POs) may be used for the aperiodic triggering of positioningmeasurement reporting. For example, one or more of following may apply:

-   -   Receiving a paging indication in the subset of Paging Occasions        (Pos) may be considered as the aperiodic triggering event for        positioning measurement reporting    -   A specific RNTI (e.g., P-RNTI or Pos-RNTI associated with        aperiodic triggering of positioning measurement reporting) may        be used to indicate the aperiodic triggering        -   A DCI with the Pos-RNTI may schedule the PDSCH, wherein            positioning measurement reporting related information may be            included. The positioning measurement reporting related            information may comprise at least one of            -   The WTRU identity for which the positioning measurement                reporting is triggered            -   One or more positioning measurement resources            -   One or more SRSp resources for transmission            -   Uplink resources to use for reporting        -   A DCI with the Pos-RNTI may include a direct indication of            which WTRU is triggered for the reporting. For example, a            bitmap may be included and a bit position in the bitmap may            be associated with a WTRU identity. When the bit position            associated with a WTRU indicates TRUE (e.g., 1), the WTRU            may be triggered to report the positioning measurement;            otherwise, the WTRU is not triggered to report

In various embodiments, aperiodic triggering of positioning measurementreporting may be used interchangeably with: 1) aperiodic triggering; 2)activation/deactivation of semi-persistent positioning measurementreporting; and/or 3) configuration of periodic positioning measurementreporting.

Condition Based Measurement Reporting Method

In one embodiment, the WTRU may transmit a positioning report on anavailable CG resource if RSRP is above a configured threshold. Suchthreshold may be the same threshold configured for small datatransmission. If RSRP is less than the threshold, the WTRU may transmitthe positioning report on a RACH resource or an SDT RACH resource andthe WTRU may request a resource for subsequent transmission if thereport does not fit within the PUSCH resource associated with the RA(i.e. the MSGA payload or the Msg3).

The WTRU may select a positioning method based on (a) the selectedresource for transmitting the positioning report, (b) a channelmeasurement (e.g., RSRP or SINR), and/or (c) the selected SSB associatedwith the CG on which the positioning report is transmitted. In oneexample, the WTRU may select a certain positioning method and/orresource (e.g., PRS or SRSp) based on the channel condition. Apositioning method may comprise at least: DL based positioning, UL basedpositioning, PRS based positioning, SRSp based positioning, timedifference of arrival based positioning, and/or multi-RTT basedpositioning, among others. In one example, the WTRU may select a DLbased positioning method if channel conditions (e.g., RSRP or SINR) areworse—or better—than a configured threshold (e.g., in cell edgeconditions). The WTRU may select an UL based positioning method ifchannel conditions are better than a configured threshold. The WTRU mayselect an RTT based positioning method (e.g. multi-RTT) when channelconditions are better than a configured threshold (e.g.RSRP(s)>threshold, or RSRP differential is within a configure range).The WTRU may measure RSRP from more than just the serving cell todetermine the selected positioning method.

The WTRU may select a positioning reporting method (e.g. the selectedresource for reporting the positioning report) based on a channelmeasurement (e.g., RSRP or SINR), uplink time alignment, and/or based onthe selected SSB associated with the CG on which the positioning reportis transmitted. In one example, the WTRU may transmit a positioningreport on a CG valid for small data transmission (e.g., valid in thesense that its TA timer is running, and in the same serving cell inwhich its configuration was received) if measured channel conditions(e.g., RSRP or SINR) are above a configured threshold or within aconfigured range, and/or if the WTRU is uplink timing aligned.Otherwise, the WTRU may select a PRACH resource to transmit thepositioning report.

Measurement Reporting over Control Plane (CP) WTRU Sends the PositioningInformation to the Network in an SDT via Control/Use Plane

In one embodiment, the WTRU may be assigned with a priority valueassociated with an SRB when sending measurement reports and/or locationinformation to the network in small data transmission (SDT) while in RRCInactive/idle mode. For sending the measurement report and/or locationinformation in an SDT to the RAN/LMF via the control plane (via AMF) inone or more NAS messages/PDUs, the WTRU may use the priority valueassigned to either SRB1, SRB2 or any SRB, for the following:

-   -   Requesting the UL grants using the LCG/BSR procedure    -   Multiplexing the NAS PDU in the received UL grant using the LCP        procedure

For sending the NAS PDUs in an SRB (e.g. SRB2) using SDT, the WTRU maysend a request to the network to activate the security associated withthe SRB. The request for security activation may be sent in a separateRRCResumeRequest message prior to sending the SDT containing the NASPDUs. Alternatively, the request for security activation may be senttogether with the SDT when sending the NAS PDU.

For activating the security for an SRB (e.g., SRB2), the WTRU may usethe security related information (e.g., security keys and next hopchaining counter) which may be previously received in an RRCReleasemessage and stored as part of the WTRU context when transitioning to RRCInactive/Idle mode. For example, the WTRU may include a resume causevalue for indicating control plane forwarding and/or security activationwhen sending the NAS messages in the SDT. The security activation mayalso enable the RAN to activate the security and integrity protectionfor the SRB to carry the NAS PDUs in the SDT in the control plane fromWTRU to LMF via AMF. In the case when sending a separateRRCResumeRequest, the WTRU may use the SRB (e.g., SRB2) for carrying theNAS PDUs upon receiving an indication message (e.g., in a RRCResumemessage) acknowledging control plane forwarding and/or securityactivation for the SRB. The indication message received by the WTRU mayalso contain an indication for using SDT for the SRB (e.g., SRB2) whileremaining in RRC Inactive/Idle mode without transitioning to RRCConnected mode.

In one example, the one or more SRBs carrying the NAS PDUs may beassigned with priority values which are higher by default than thoseassigned to DRBs for sending data in SDT. In another example, differentSRBs may be associated with different priorities which may be carryingNAS messages whose priorities may depend on the positioning service. Forexample, a WTRU supporting a positioning service with moderate latencyrequirements may be configured with one or more SRBs with relatively lowpriority when using SDT. In this case, it may be possible for the SRB(s)carrying NAS messages to be assigned with lower priority compared toother high priority DRBs using SDT.

In another embodiment, the WTRU may send the location information and/ormeasurement reports to the RAN/LMF via the user plane (via UPF) in oneor more DRBs configured to be used with SDT. In this case, for example,the different DRBs may be assigned with different priority values andthe WTRU may use the DRBs for sending positioning information in SDTbased on the priority assigned to the poisoning service.

WTRU Sends Positioning Information Using SDT Based on Configured DataVolume Threshold

In one embodiment, the WTRU (operating in INACTIVE state) may send oneor more types of positioning information (e.g., measurement reportsand/or location information) using SDT configured for one or more SRBsbased on a data volume threshold configured and/or associated with theSRBs. In this case, the different SRBs (e.g., SRB1, SRB2, SRB3) may beconfigured in the WTRU, possibly for carrying the positioninginformation in NAS messages using SDT. The different SRBs configured forSDT in the WTRU may be configured with one or more data volume thresholdvalues, possibly associated with the different types of positioninginformation (e.g., location estimate, measurement reports associatedwith PRS(s), Rx-Tx time difference measurement for multi-RTT methods).The data volume threshold may be used for resuming the SRBs (e.g., SRB2)configured for SDT when triggered by the arrival of a NAS message from ahigher layer, possibly containing positioning information. In anexample, the WTRU may resume SRB2 for transmitting RRC message and/orNAS message in SDT when the size of the RRC/NAS message is less than orequal to the data volume threshold configured for the SRB2. The datavolume threshold may be configured by the LMF or gNB, for example. Asimilar approach used for sending positioning information using SDT whenthe WTRU is in INACTIVE state may also be applied when the WTRU is inIDLE state, for example.

In another example, the WTRU may be configured with one or more SRBs,which may be used for carrying positioning information in SDT based onthe size of the positioning information determined by the WTRU. In thiscase the WTRU may be configured with a data volume thresholdcorresponding to the SRB(s), based on an indication sent by the WTRU tothe network (e.g., gNB) indicating the size of the positioninginformation to be carried using SDT. For example, upon receiving alocation request from the network (e.g., LMF), the WTRU may indicate tothe serving gNB the size of the positioning information to be sent in ULwhen operating in INACTIVE state. The WTRU may send the indication ofthe size of the positioning information to the gNB either in an RRCmessage, MAC CE, or UCI, for example. The WTRU may send the indicationto the gNB either before, during, or after transitioning to INACTIVEstate, for example. Upon being configured with the corresponding datavolume threshold, the WTRU may then send the positioning information inRRC/NAS message(s) in the associated SRB (e.g., SRB2) using SDT.

In another example, each SRB configured for SDT (e.g., SRB1, SRB2) inthe WTRU may be associated with different data volume thresholds atdifferent times, where at any given time at least one data volumethreshold may be activated for the SRBs. The different data volumethresholds may be associated with a flag or an indicator, which may beused during triggering of SDT procedure. For example, a default datavolume threshold may be activated and applicable when initially the SRBis configured for SDT. In an example, the WTRU may be configured with adefault/first data volume threshold which may be aligned with or higherthan the size of NAS messages carrying positioning information (e.g.,measurement report). In another example, the data volume threshold maybe dynamically changed/updated based on triggering of the SDT procedure,for example. In this case, upon the arrival of an NAS message of acertain size, the WTRU may initially determine if the NAS message isless than the default/first data volume threshold for determiningwhether the NAS message can be sent with SDT. In the case when the NASmessage is determined to be higher than a first data volume threshold(e.g., the aforementioned default value) and less than or equal to asecond configured data volume threshold greater than the first datavolume threshold, the WTRU may trigger the SDT procedure by sending aresume request (e.g., in MSGA, MSG3, or CG) to the network containing anindicator/flag associated with the second data volume threshold. TheWTRU may send the NAS message upon receiving a resume message (e.g., inRRC) indicating the activation of the second data volume threshold. Inthis case, the WTRU may continue sending the one or more NAS messages(e.g., carrying positioning information) so long as the second datavolume threshold remains activated and/or not deactivated by thenetwork, for example. The aforementioned data volume threshold may beconfigured by the LMF or gNB, for example.

In another example, the WTRU may determine the attributes of positioninginformation to be sent using SDT, including the type and size of thepositioning information, based on the data volume threshold(s) that maybe configured and/or activated for the associated SRB (e.g., SRB1,SRB2). For example, the WTRU may determine whether the positioninginformation (i.e., carried in a NAS message) is to be segmented intomultiple segments based on the data volume threshold configured in theWTRU and/or associated with the SRB for carrying the positioninginformation. In this case, the WTRU may segment the positioninginformation into different segments which may be smaller than or equalto the configured data volume threshold, for example. In anotherexample, the WTRU may segment the positioning information into severalsegments, where the number of segments may be determined based on alatency requirement associated with positioning configured in the WTRU.For example, the WTRU may use the data volume threshold and/or theconfigured positioning latency requirement, possibly related to arequirement where the positioning information is to be sent within alatency bound, for determining the number of segments to be made whensegmenting the positioning information. The WTRU may then send thedifferent segments containing the positioning information using SDT.

In another example, the WTRU may determine the type and amount ofpositioning measurements to be made and/or sent as a measurement reportto the network based on the configured data volume threshold(s)associated with the SRBs (e.g., SRB1, SRB2) when using SDT. For example,the WTRU may be configured with one or more PRS configurations formaking measurements on the DL-PRS and sending the measurement reports tothe network. The different types of measurement reports that may be sentby the WTRU may be associated with different positioning accuracies, forexample. In an example, the WTRU may determine whether to send richmeasurement reports (e.g., measurements with higher granularity,possibly containing information/labels on multipath and/or interference)or normal/simplified measurement reports (e.g., measurements with aminimum configured granularity) based on the configured data volumethreshold. In this case, the WTRU may send rich measurement reports,containing timing of arrival or angle of arrival measurements foradditional paths at higher resolution, for example, when the data volumethreshold configured for SDT in SRB2 is higher than or equal to the sizeof the NAS message carrying the rich measurement reports.

WTRU Indicates RAN Configuration to LMF for Supporting PositioningProcedures Based on WTRU RRC State

In one embodiment, the WTRU may send information indicating its RANconfiguration, including its RRC state and/or configuration to beapplied in the RRC state, to the LMF for receiving the positioningassistance information and/or measurement reporting configurationassociated with the RAN configuration. For example, the WTRU may send anindication to the LMF when transitioning from CONNECTED state toINACTIVE state such that the WTRU may receive the assistance information(e.g., PRS configuration) and/or measurement reporting configurationthat may be applied when the WTRU operates in INACTIVE state. The WTRUmay send the aforementioned indication to the LMF via LPP.

In an example, the WTRU may receive one or more positioningconfigurations (e.g., assistance information, positioning reportingconfiguration) containing an update to the QoS requirements associatedwith positioning, including positioning accuracy and/or latency, basedon the information sent by the WTRU to the network about its RRC state.In this case, the configuration received by the WTRU may enable the WTRUto flexibly balance the trade-offs in terms of achieving highpositioning accuracy, high device efficiency (i.e. low powerconsumption) and/or low latency positioning, for example.

In an example, the WTRU may receive assistance information, containingone or more PRS configurations, to be used for making measurements whenoperating in INACTIVE/IDLE state based on the indication sent by theWTRU to the network about its current and/or future RRC state. The WTRUmay receive the assistance information/PRS configuration to be used whenthe WTRU is operating in a particular RRC state, for example. Forexample, the WTRU may use a first PRS configuration when operating inCONNECTED state and a second PRS configuration when operating inINACTIVE state. In this example, the use of the first PRS configurationmay result in longer measurement duration, with possibly higher accuracyat the WTRU. Alternatively, the use of the second PRS configuration mayresult in lower power operation and shorter measurement duration at theWTRU, possibly with reduced accuracy.

In another example, where the WTRU may be configured with SDT forsending data (e.g., positioning information) when in INACTIVE state, theWTRU may receive a measurement reporting configuration from the network(e.g., LMF) indicating the one or more parameters to be used whensending the measurement reports when in INACTIVE state. The parametersassociated with measurement report configuration received by the WTRUmay include the type of measurements to be reported (e.g.,rich/simplified reporting), the amount of measurements to be reported(e.g., the size of each measurement report), and/or the periodicity ofreporting, for example. Whether reporting is simplified or rich may bedetermined by the number of additional paths for which the WTRU reportsmeasurements. For example, in a simplified report, the WTRU may reportthe PRS measurements related to the main path. In a rich report, theWTRU may report the PRS measurements related to the main path and Nadditional paths, where N may be configured by the LMF. The parametersfor measurement report configuration may be received from LMF based onthe information sent by the WTRU on the data volume threshold configuredfor SDT, in one or more SRBs/DRBs, for example. For example, the WTRUmay be configured to send simplified measurement reports, possibly withreduced granularity, in INACTIVE state based on the awareness at the LMFof the (lower) data volume threshold configured for SDT.

In another example, the WTRU may send the configuration information forINACTIVE mode operation, including the information on the SRB/DRBs(e.g., SRB2) configured for SDT and/or the associated data volumethreshold configured for SDT, to the LMF. The WTRU may send theaforementioned information to the LMF via LPP. The configurationinformation for INACTIVE mode operation may be sent by the WTRU to theLMF, upon receiving one or more of the following signaling/messages:

-   -   Higher layer location request (e.g., MO-LR, MT-LR)    -   (LPP) Capability transfer request    -   (LPP) Assistance data transfer    -   (LPP) Location request transfer request    -   (LPP) Positioning information transfer

The configuration information for INACTIVE operation also may be sent bythe WTRU to the LMF when receiving a first INACTIVE mode configurationfrom a gNB and/or when an update to the INACTIVE mode configuration istriggered and is received by WTRU, for example. In an example, where theWTRU may have transitioned to INACTIVE state, the WTRU may send theindication to the LMF on the first/updated INACTIVE mode operationconfiguration in a NAS message. For example, the WTRU may send theindication in an NAS message in either MSG A, MSG 3 or CG in the resumemessage when triggered by an update to the INACTIVE mode configuration(e.g., change in the data volume threshold), for example.

An LMF is a non-limiting example of a node or entity (e.g., network nodeor entity) that may be used for or to support positioning. Any othernode or entity may be substituted for an LMF and remain consistent withthis disclosure.

Beam Management for CG

Beam Management during Configuration for CG.

In various embodiments, “PRS” and “PRS resource” may be usedinterchangeably. Also, “PRS”, “DL PRS” and “Downlink PRS” may be usedinterchangeably.

Conditions to Use CG Based Measurement Reporting for PositioningCondition to Proceed to Use Configured Grant for Measurement Reporting

The WTRU may be (pre)configured with PRS configurations by LPP duringthe RRC connected state. In an embodiment, at least one of the followingconditions should be satisfied for the WTRU to perform measurementreporting for positioning using the configured grant (CG).

-   -   The WTRU is configured with a valid timer for the configured        grant    -   The WTRU receives at least one SSB that satisfies the        (pre)configured criterion, e.g., RSRP of the received SSB is        above the (pre)configured threshold    -   The WTRU has PRS configurations in LPP Assistance Data    -   If the WTRU receives at least one SSB which satisfies the        (pre)configured criterion, the WTRU also receives at least one        PRS resource which satisfied the (pre)configured criterion        (e.g., RSRP of the received PRS is above the (pre)configured        threshold)    -   The WTRU performs WTRU assisted positioning or WTRU based        positioning

The above conditions can be combined so that the WTRU can be configuredwith configured grants based on multiple conditions.

The WTRU may receive PRS configurations after the WTRU receivesconfiguration for the CG. In that case, the WTRU may send a request forPRS configurations by sending the LPP Request Assistance Data to the LMFin the CG so that the WTRU can receive PRS configurations. The WTRU maysend the request to the network in RRCResumeRequest, message 3 ormessage A.

Definition of 2 Sets of Association, SSB<->CG, SSB<->PRS/SRSp Definitionof 2 Sets of Association Rules

The WTRU may use a configured grant resource to transmit measurementreports to the network. If the WTRU is not configured with theconfigured grant resource, the WTRU may perform the following procedureto obtain configuration for the configured grant.

In one embodiment, the WTRU may receive two sets of association.

-   -   In the first set of associations, each SSB (SS block) may be        associated with a configured grant (CG) resource. Alternatively,        multiple SSBs may be associated with one configured grant        resource or multiple configured grant resources can be        associated with one SSB.    -   In the second set of associations, information regarding spatial        relation or QCL relationship between the SSB and other reference        signals, such as PRS, or channels may be included. Examples of        different types of QCL can be found in 3GPP Technical        Specification. 38.214.

How Association is Stored at the WTRU

The WTRU may receive the aforementioned sets of associations via ahigher layer during RRC connected state or after transition to RRC IDLEor INACTIVE mode. The WTRU may receive the aforementioned sets ofassociations by RRCRelease message, RRC, or LPP message.

SSB Reception: Procedure for Measurement Reporting

For example, the WTRU may perform the following procedure to returnmeasurement reports to the network.

-   -   1. The WTRU selects an SSB among multiple SSBs transmitted from        the gNB according to the (pre)configured criterion. The        criterion may be whether RSRP of the SSB received by the WTRU is        above the preconfigured threshold;    -   2. The WTRU receives the PRS that is associated with the        selected SSB, where the association is indicated in the second        set of associations;    -   3. The WTRU performs measurements using the received PRS;    -   4. The WTRU transmits the measurement reports to the network in        the configured resource the selected SSB is associated with.

Multiple SSBs to One CG or Multiple CGs to One SSB

Multiple SSBs may be associated with one configured grant such that theWTRU can flexibly determine an SSB beam during mobility, for example.One SSB may be mapped to multiple CG resources so that the WTRU maydetermine to use multiple CG resources to send measurement reports onmultiple measurement reporting occasions where there is a one-to-onecorrespondence between measurement reporting occasion and CG resource.In addition when one SSB is mapped to multiple CG resources, i.e., agroup of CG resources, CG resources between groups do not overlap sothat collision can be avoided.

For example, in the second set of associations, the WTRU receivesassociation between SSB and other RS or channels and association may berelated spatially. For example, the WTRU may receive a configurationthat indicates a spatial quasi co-location relationship related toQCL-TypeD, between an SSB and a PRS resource. There could be a PRS thatcan be transmitted in the same direction as the SSB from the samelocation. In other words, the WTRU may assume that the same Tx(transmission) spatial filter is used to transmit SSB and PRS.

In the first set of associations, an identification number of an SSB andresource identification number of configured grant resource may beassociated, for example.

As the WTRU may receive SSB from both the serving cell and a neighboringcell, the WTRU may use the first set of associations that associates aconfigured grant resource(s) and SSB from the serving cell.

As the gNB does not know which SSB the WTRU may choose, the WTRU mayreceive multiple variants of the first set of associations wheredifferent SSBs are within each variant.

SSB Reception+PRS Beam Sweeping: Procedure for Measurement Reporting

In an embodiment, in the second set of associations, there may bemultiple PRS resources associated with the selected SSB. With referenceto the flowchart of FIG. 12 , the WTRU may perform the followingprocedure to return measurement reports to the network.

-   -   1. After receiving a SSB (1201), the WTRU selects an SSB from        among multiple SSBs transmitted from the gNB according to a        criterion (1203). The criterion may be whether RSRP of the SSB        received by the WTRU is above a preconfigured threshold.    -   2. The WTRU determines the PRS to receive according to        association with the SSB (1205).    -   3. The WTRU receives the PRS that is associated with the SSB,        where the association is indicated in the second set of        associations (1207). The WTRU may receive PRS resources in        different symbols or slots that have unique association with the        PRS resources. The WTRU may receive information about        association between PRS resources and symbols/slots in        RRCRelease, RRC, LPP message, or higher layer signaling.    -   4. The WTRU selects the PRS that satisfies the (pre)configured        criterion, which the WTRU may receive in RRCRelease, RRC, LPP        message, or higher layer signaling (1209).    -   5. The WTRU performs measurements using the PRS the WTRU        received (1211).    -   6. The WTRU transmits the measurement reports to the network at        the configured resource the selected SSB is associated with        (1213).

The WTRU transmits the measurement reports to the network at theconfigured resource the selected SSB is associated with.

Definition of Two Sets of Association Rules for SRSp

In another example, in the first set of associations, each SSB may beassociated with a configured grant resource. The second associationinformation contains spatial relation or QCL regarding the SSB with SRSfor positioning. In this disclosure, “SRSp” and “SRSp resource” may beused interchangeably.

The WTRU may implement the following procedure to transmit SRSp.

-   -   1. The WTRU selects an SSB according to a criterion from among        multiple SSBs transmitted from the gNB;    -   2. The WTRU finds the SRSp that is associated spatially with the        SSB the WTRU selected, and transmits the SRSp in the configured        grant resource the selected SSB is associated with.

In another embodiment, the first set of associations concernsassociation between PRS and configured grant resource. The secondassociation concerns association between SSB and multiple PRSs regardingspatial or QCL information. In this case, once the WTRU chooses the SSB,the WTRU chooses one of the PRSs associated with that SSB. The WTRUexpects to send measurement reports in the configured grant resourcethat is associated with the chosen PRS.

Assumption of Beam Correspondence for SRSp

The WTRU may determine to transmit the SRSp using the spatial filter ithas used to receive the SSB that the WTRU selected. In such case, theWTRU does not need to receive the second set of associations whichcontains association between SRSp and SSB in terms of spatial relationor QCL relationship. Configuration to allow the WTRU to determine the TXspatial filter may be explicit or implicit. The WTRU may receiveexplicit indication in higher layer signals such as RRCRelease, LPPmessage, or RRC. The WTRU may receive an implicit indication todetermine to transmit SRSp using the spatial filter it used to receivethe SSB, if it does not receive the second set of associations.

Only Given Association between SSB and CG: WTRU Reports Back theSelected SSB

In another embodiment, the WTRU may be configured with the first set ofassociations only. In that case, the WTRU may transmit information aboutthe SSB that the WTRU selected at the configured grant resource that isassociated with the SSB selected by the WTRU. The WTRU may sendinformation about the selected SSB, such as resource ID inRRCResumeRequest, message 3, or message A during the RACH procedure.After the transmission, the WTRU may receive from the network the secondset of associations. The second set of associations contains spatialinformation or QCL relationship between the selected SSB and PRS.

Only Given Association between SSB and CG: The WTRU Asks for PRSAssistance Data

In another embodiment, the WTRU may receive configuration for the CGbased on the first set of associations. If the WTRU is not configuredwith PRS, the WTRU may send LPP assistance data in the CG to ask the LMFfor the PRS configuration.

The WTRU May have PRS Configuration Already, Passed Down fromRRC_CONNECTED: The WTRU May Trace Backward to Obtain the CGConfiguration

The WTRU may receive PRS configurations during RRC Connected state. TheWTRU may keep the configuration even after transition to RRC IDLE orINACTIVE mode. Thus, after transition to RRC IDLE or INACTIVE mode, theWTRU may receive the same PRS as the one the WTRU received during RRCConnected state. The WTRU may determine the CG resource by theconfigured first and second sets of associations. For example, the WTRUmay determine the CG resource by the following steps.

-   -   1. The WTRU determines the SSB that is associated spatially with        the PRS the WTRU was configured during RRC Connected state.    -   2. The WTRU determines the CG resource that is associated with        the SSB selected in the first step.

The WTRU may determine the CG resource and send the measurement reportsassociated with the PRS that the WTRU is configured with.

How Association is Obtained

The WTRU may receive the above first and second sets of associations inhigher layer information, such as RRCRelease, LPP message relatedsignaling, or WTRU context.

Special Cases of Association

The association may be defined to be used during IDLE/INACTIVE modepositioning. For example, the association may be limited to SSB, PRSresources, or SRSp resources that are used during the RRC Connectedstate.

Other Cases Source of SSBs

In this disclosure, the SSB used in an association may be from theserving cell or a neighboring cell. In either case, the cell IDindicating which cell the SSB is transmitted from is also included inthe association information which the WTRU uses to determine thetransmission source of the SSB and CG resource, PRS, or SRSp which isassociated with the SSB.

The WTRU May Not Need to Measure SSBs if They are Already Provided inAssistance Data

The WTRU may receive the assistance data from the LMF containingconfigurations of PRS and/or SSBs transmitted in the serving orneighboring cells during IDLE/INACTIVE mode or RRC Connected state. TheWTRU may receive the assistance data by broadcast. In anotherembodiment, the WTRU may receive RRC configuration about SSBstransmitted from the TRPs. In such a case, if the WTRU receives thefirst set of associations, the WTRU may determine configurations of theCG without measuring SSBs. The WTRU may send a request for theassistance data to the network in RRCResumeRequest, message 3, ormessage A.

MO-LR

WTRU Sends the LCS Request for MO-LR Positioning Service while in RRCInactive/Idle Mode

In one embodiment related to MO-LR where the request for positioninginformation originates from the LCS client located in the WTRU, the WTRUsends the positioning information request to the network (i.e., RANand/or LMF) while remaining in RRC idle/inactive mode. Specifically, therequest for positioning information (i.e., LCS request) may be sent tothe network, either in a control plane NAS message (e.g., sent via AMFto LMF) or a user plane message (e.g., sent via UPF to LMF). In additionto the LCS request, the WTRU in RRC inactive/idle mode may also send oneor more of the following to the network:

-   -   WTRU capability information for positioning        -   For example, the WTRU may send the capability to support one            or more positioning methods and/or configurations, including            RAT-dependent (e.g., DL-based on PRS measurement (DL-TDoA or            DL-AoD) or UL-based on SRSp transmission (UL-TDoA or            UL-AoA)) and RAT independent methods (e.g., GNSS).    -   Request for assistance information        -   For example, the WTRU may request one or more PRS and/or            SRSp configurations for supporting one or more positioning            methods. The WTRU also may indicate the PRS/SRSp            configurations that may be or are currently            supported/available at the WTRU.

In one example, the WTRU may piggyback the WTRU capability informationfor positioning and/or request for assistance data onto an LCS request.In this case, the WTRU may send one or more of the aboveinformation/requests, upon encapsulation, either in a singletransmission (e.g., single NAS message) or in multiple transmissions(e.g., multiple NAS messages). When sending in a single transmission,the WTRU may send the NAS message, possibly in a RRCResumeRequest orSDT, either in MsgA (i.e., when using 2-step RACH), Msg3 (i.e. whenusing 4-step RACH), or using a CG preconfigured in the WTRU. Likewise,when sending in multiple transmissions, the WTRU may send the NASmessage(s) in multiple SDTs (e.g., multiple MsgA, Msg3, or CGs) whileremaining in RRC inactive/idle mode.

In another example, it may be possible for a WTRU operating in RRCidle/inactive mode to skip the transmission of the WTRU capabilityinformation and/or the request for assistance information when sendingthe LCS request to the network. The decision of whether to send theabove information/request may be made by the WTRU based on one or morevalidity conditions associated with the WTRU capabilities and/orassistance information. The validity conditions may be monitored by theWTRU upon receiving the trigger from the LCS client, for instance. As anexample, it may be possible for the WTRU to have previously sent theWTRU capability and/or received the assistance information during RRCConnected mode. The WTRU may also be configured or provided withvalidity condition(s) (e.g., timer, cell IDs in RNA/TA, PLMNrestrictions) when transitioning to RRC inactive/idle mode, in aRRCRelease message, for example. In this case, the WTRU may determinewhether to include or exclude the WTRU capability information and/orrequest for assistance information based on whether the validityconditions are valid (e.g., timer is not expired or cell IDs are valid)when triggered by the LCS client and/or sending the LCS request to thenetwork.

In another example, the decision of whether to send the WTRU capabilityinformation and/or (request) assistance information while operating inRRC inactive/idle mode may be made based on the reception of a requestmessage from the network either before or after sending the LCS requestto the network. In this case, the WTRU in RRC inactive/idle mode maysend the WTRU capability information or assistance data information(e.g., PRS configurations supported) upon receiving a request from thenetwork in a NAS message, which may be sent in a paging or RRCReleasemessage or RRCResume message, for instance. As an example, the requestfor WTRU capability and/or information on assistance data may betriggered by network (e.g., LMF) upon receiving the LCS request from theWTRU and/or determining that the context related to the WTRUcapability/assistance data is either not available or not valid (e.g.,at the AMF or LMF).

WTRU Receives Response Messages(s) Associated with MO-LR PositioningService while in RRC Inactive/Idle Mode

Upon sending the LCS request for MO-LR service and/or the information onWTRU capability/assistance data, the WTRU may receive one or moreresponse messages containing one or more of the following:

-   -   Response to LCS request for acknowledging the support for        providing WTRU positioning information    -   Request for WTRU capability information    -   Assistance data, comprising one or more PRS/SRSp configurations,        for the WTRU to use for determining positioning while operating        in RRC inactive/idle mode    -   Configuration for sending measurement reports, comprising        information on resources to use (e.g., CG), periodicity for        reporting, etc.

In one example, the WTRU may receive the response message(s) in one ormore RRCRelease messages (e.g., in Msg B in 2-step RACH or Msg4 in4-step RACH), upon sending an RRCResumeRequest message. For a WTRUoperating in RRC inactive mode, the response message(s) may be receivedin an RRCRelease message under the suspendConfig configuration, forinstance. In another example, the WTRU may receive the responsemessage(s) in one or more RRCResume messages (e.g., Msg B or Msg 4). TheWTRU also may receive the response message(s) containing one or more ofthe above information in a (RAN/CN) paging message, for example.

Reporting Bypassing Control Plane

WTRU-Based Positioning does Not Require Measurement Reporting

In one embodiment, for the WTRU-based positioning, the WTRU maytransition to the RRC Connected state to report the location of theWTRU. For instance, the WTRU may report a (pre)configured number ofpositions after the WTRU transitions to the RRC Connected state. In thiscase, the WTRU may be configured not to report measurements or estimatedlocation while the WTRU is in IDLE or INACTIVE mode.

The (pre)configured number of positions reported may be the locations ofthe WTRU estimated at various times while the WTRU was in the IDLE orINACTIVE state. The location of the WTRU may be obtained after the WTRUestimates its own location after measuring PRSs transmitted from TRPs.The WTRU may estimate its location after collecting measurements such asAoD, AoA, RSTD, and/or ToA for each PRS or multiple PRSs transmittedfrom the TRP(s). Multiple location can be associated with different timestamps, indicating each location is estimated at different timeoccasion.

The WTRU may report statistical characteristics of the multiplelocations, which may include at least average value of multiplelocations (e.g., geometric center of multiple locations), and/orstandard deviations of multiple locations. The aforementionedcharacteristics may be reported after the WTRU transitions to the RRCConnected state. Particularly, reporting an accumulated number oflocations reduces the number of times that the WTRU must send a report,thereby reducing power consumption for transmitting the reports.

The WTRU may receive an indication from the network to return to the RRCconnected state to report estimated location(s). The WTRU may receivethe indication in RRC or LPP messaging.

The WTRU may be configured with the number of positions to report byhigher layer message, such as RRC, RRCRelease message, or LPP.

In another embodiment, the WTRU may report the plurality of(pre)configured positions using message 3, message A, or CG duringINACTIVE mode.

Positioning Handover during Mobility Limited to IDLE/INACTIVITY Mode

WTRU in Idle/Inactive Mode Assists the Network in Aligning the TrackingArea and/or RNA Configuration with the PRS/SRSp Configuration

In various embodiments, the WTRU sends an indication to the networkwhile operating in idle/inactive mode for aligning the configurationparameters (e.g., cell IDs) associated with the PRS/SRSp configurationswith those of the Tracking Area and/or RAN notification Area (RNA)configured in the WTRU. In the case of idle mode, the WTRU may beassigned a Tracking Area list consisting of the list of cell IDs inwhich the WTRU may be mobile without having to send a Tracking Areaupdate message to the network. In the case of inactive mode, the WTRUmay be assigned with an RNA list consisting of cells IDs where the WTRUmay be mobile without sending the RNA update (RNAU) message to the RAN.The WTRU may be provided with the PRS configurations along with theassociated cell IDs in the assistance information, which may bemaintained and used by the WTRU for DL-based and/or UL+DL basedpositioning during idle/inactive mode. Similarly, the WTRU may beconfigured with SRSp resources along with the associated cell IDs forUL-based and/or UL+DL based positioning while in idle/inactive mode.

In this case, it is possible for the WTRU during mobility to usePRS/SRSp configuration parameters (e.g., cell IDs associated with PRSconfigurations and/or SRSp resources) which may not be aligned with thecells/gNBs associated with TA/RNA for use during idle/inactive mode. Asa consequence, the WTRU may have a mismatch in the on-duration of theDRX cycle for receiving the PRS in DL and/or transmitting SRSp in ULduring idle/inactive mode, hence resulting in possible inefficientresource usage, power waste, and inaccuracy in positioning measurements,for example. By aligning the PRS/SRSp configuration parameters with theTA/RNA parameters, the WTRU may receive PRS or transmit SRSp in thesimilar time slots when receiving paging messages or transmittinginitial access messages during mobility while in idle/inactive mode. Inaddition, the WTRU may also be configured to send/receive measurementreports which can possibly be correlated with the TA/RNA update messagessent to the network or paging messages received from network.

In one embodiment, the WTRU may assist the network in correlating theTA/RNA configurations and the parameters associated with the PRS/SRSpconfigurations for enabling the WTRU to support different positioningmethods during mobility while remaining in idle/inactive mode. In thiscase, upon receiving the PRS/SRSp configurations and the associated cellrelated parameters (e.g., in SIB, CN/RAN paging messages), the WTRU maycompare the cell IDs associated with the PRS/SRSp configurations and thecell IDs in the TA/RNA for determining the TA/RNA configuration forpositioning. The TA/RNA configurations for positioning may be either thesame as or different from the TA/RNA configurations used for CN/RANpaging, for example. Based on the identification of the cell IDs thatare common and different in both configurations, the WTRU may thenperform one or more of the following:

-   -   the WTRU may send an indication to the network when it        identifies at least one cell ID that may be different between        the TA/RNA lists and PRS/SRSp configuration parameters (e.g.,        cell list)    -   The WTRU may select a TA/RNA configuration for positioning from        one or more pre-configurations, which may consist of different        lists of cell IDs that may match with the cell related        parameters associated with PRS/SRSp configurations. The WTRU may        then send an indication to the network comprising the selected        TA/RNA configuration for positioning    -   The WTRU may determine/derive the parameters (e.g., cell IDs)        for updating the TA/RNA list for positioning and send the        updated parameters to the network    -   The WTRU may send the assistance information to the network for        correlating the PRS configuration with the TA/RNA list for        positioning

In the case when the WTRU sends indication for aligning the parametersin TA/RNA and in PRS/SRSp configurations, the WTRU may include one ormore of the following information in the indication:

-   -   WTRU ID: For example, the WTRU may include the CN assigned IDs        (e.g., S-TMSI, IMSI) and/or RAN assigned IDs (e.g., I-RNTI). In        another example, the WTRU may select a random ID from a pool of        IDs configured in the WTRU when sending the indication to the        network.    -   Parameters related to PRS/SRSp configuration: For example, the        WTRU may indicate the identifiers of PRS/SRSp configurations        that may be currently aligned or to be reconfigured for aligning        with the TA/RNA    -   Parameters related to TA/RNA: For example, when sending the        indication to the LMF/RAN, the WTRU may indicate the one or more        parameters including number of cells and/or cell IDs associated        with PRS/SRSp that may be different from those in the TA/RNA. In        one example, the WTRU may include in the indication the RACH        resources and/or the identifier of the RACH resources that may        be updated when aligning with the TA/RNA list. In another        example, the WTRU may send a group ID representing one or more        cells associated with PRS/SRSp that are different from those in        the TA/RNA.    -   TA/RNA ID: For example, when the WTRU selects a TA/RNA        configuration from a set of pre-configurations, the WTRU may        indicate to the network the identifier of the selected TA/RNA        pre-configuration    -   Assistance information: For example, the WTRU may indicate        information on WTRU mobility (e.g., WTRU speed, direction)        and/or WTRU environment (e.g., blockages to LOS path, multipath)

In the case when the WTRU determines/derives the cell list for TA/RNAfor positioning based on the alignment with the cell related parametersassociated with PRS/SRSp configurations, the WTRU may determine one ormore of the following:

-   -   A number/list of Cell IDs that may be higher than the existing        list by a certain threshold, and less than the list of cell IDs        in the Tracking Area and/or RNA    -   A number/list of Cell IDs that may match with the list of cell        IDs in the Tracking Area and/or RNA    -   A number/list of Cell IDs that may be higher than the list of        cell IDs in the Tracking Area and/or RNA by a certain threshold    -   A number/list of Cell IDs that may be determined based on a        combination of cell IDs within the RNA and Tracking Area

The criteria for determining the updated number of cells associated withthe PRS/SRSp configurations, including the threshold number of cells,may be (pre)configured in the WTRU. The criteria and the thresholds maybe determined based on balancing the tradeoff between having a widerarea for performing positioning and having to send more positioningmeasurement reports during mobility while remaining in idle/inactivemode, for example. As an example, the WTRU may be configured todetermine a number of cells that is less than the cell count in theTA/RNA if the WTRU is intended to send frequent number of measurementreports in TA/RNA update message while being mobile within a smallerarea. Likewise, the WTRU may be configured to determine a number ofcells that is higher than the cell count in the TA/RNA if the WTRU isintended to send fewer measurement reports in the TA/RNA update messagewhile being mobile in a wider area.

The WTRU may send the indication to the network for aligning TA/RNA andthe PRS/SRS configurations in either a TA/RNA update message or in aninitial access message (e.g., Msg 1/3 or Msg A) based on one or more ofthe following triggering conditions:

-   -   Detection of different cell ID during mobility    -   Detection of different PRS from the configured PRS    -   Reception of paging message    -   Timer (e.g., for periodic transmission of indication message)    -   Measurements made at WTRU    -   Higher layer/application trigger

Upon aligning the parameters, the parameters corresponding with thePRS/SRSp configurations (e.g., cell IDs, SRSp resources) may beassociated with the WTRU context and maintained along with TA/RNA in thenetwork (e.g., at the Access and Mobility Management Function (AMF) inthe CN for the Tracking Area or at an anchor gNB in RAN for RNA) and/orWTRU. The WTRU may also be assigned an identifier/index indicating thealignment between the parameters in the TA/RNA and PRS/SRSpconfigurations. In this case, the assigned alignment identifier may bemaintained with the WTRU context along with other parameters associatedwith supporting positioning during WTRU mobility (e.g., configuredgrants for sending measurement reports). When the WTRU detects amisalignment between the parameters (e.g., difference in cell ID), theWTRU may send an indication to the network including the assignedidentifier for the network to retrieve the WTRU context from the CNfunction/anchor gNB and possibly to update the PRS/SRSp and/or TA/RNAconfigurations.

An example of signaling flow for positioning during WTRU Inactive modemobility is shown in FIG. 6 , illustrating PRS configuration and RNAalignment. The WTRU 201 is initially configured by RAN with RNA (620)prior to transitioning into RRC Inactive mode. When triggered by the LMF205 (622, 624), the WTRU 201 is provided with PRS configuration eitherin SIB, CN paging, or in RAN paging message (626). Upon triggering bypositioning mobility event 628 (e.g., identifying a new cell ID outsideof RNA or identifying cell ID associated with PRS config outside of RNAor interference from neighbor cells), the WTRU sends RNAU to the RAN toupdate RNA and/or PRS config (630). The RAN updates (632) the WTRU's RNAto align with PRS config based on information on cells associated withPRS in RNAU. The WTRU receives the updated RNA and possibly updated PRSconfig in a RAN paging message (634). The WTRU receives a LocationRequest from the LMF in a CN paging or RAN paging message (636, 638).The gNB sends PRS to the WTRU (640) and the WTRU measures DL PRS (e.g.during DRX on-duration) (642) and sends the measurement report togNB/LMF in initial access (e.g. SDT), RNAU or TAU (Tracking Area Update)message(s) (644). The gNB may transmit the report to the LMF (646).

Another example of signaling flow for positioning during WTRU Inactivemode mobility is shown in FIG. 7 , illustrating SRS configuration andRNA alignment. The WTRU is initially configured by RAN with RNA (720),prior to transitioning into RRC Inactive mode. When triggered by the LMF(722), the WTRU is provided with SRSp configuration in a RAN pagingmessage (724). Upon triggering by positioning mobility event (726), theWTRU sends RNAU to RAN to update the RNA and/or SRSp config (728). TheRAN updates the WTRU's RNA to align with SRSp config. The WTRU receivesthe updated RNA and possibly updated SRSp config in RAN paging message(730). Finally, the SRSp transmitted by WTRU (734) is measured at theRAN (736) and the measurement report is sent to the LMF (738).

An example of signaling flow for positioning during WTRU Idle modemobility, illustrating PRS configuration and Tracking Area alignment, isshown in FIG. 8 . The WTRU 201 is initially configured by the RAN withRNA (820), prior to transitioning into RRC Inactive mode. When triggered(822) by the LMF 205, the WTRU is provided with PRS configuration eitherin CN paging or in RAN paging message (824). Upon triggering by apositioning mobility event (826) (e.g. identifying a new cell ID outsideof Tracking Area or identifying cell ID associated with PRS configoutside of Tracking Area or interference from neighbor cells), the WTRUsends a TAU (828) to the AMF (207) to update Tracking Area or PRSconfig. The AMF updates the WTRU's Tracking Area to align with PRSconfig based on information on cells associated with PRS sent in TAU(834). The WTRU receives the updated Tracking Area and possibly updatedPRS config in a paging message (836). The WTRU receives a LocationRequest from the LMF in a CN paging or RAN paging message (840). TheWTRU receives and measures DL PRS (842 and 844, respectively) (e.g.during DRX on-duration) and sends the measurement report to gNB/LMF ininitial access (e.g. SDT), RNAU or TAU message(s) (846). The gNB sendsthe measurement report to the LMF (848).

WTRU in Idle/Inactive Mode Performs Measurements of DL PRS Aligned withPaging Occasions in DRX Cycle

In one embodiment, a WTRU in idle/inactive mode makes positioningmeasurements on the DL PRS which may be received along with pagingmessages in time durations aligned with the paging occasions. In thiscase, the WTRU may be (pre)configured with one or more PRSconfigurations comprising different parameters (e.g., periodicity,resources) which may be associated and aligned with different DRX cycles(e.g., consisting of different ON and sleep durations) configured in theWTRU. In another example, the WTRU may receive the PRS/SRSpconfigurations which may be aligned with the DRX cycle configured inWTRU.

The alignment between PRS reception and paging message reception may besupported by the WTRU for both CN paging and RAN paging, for example. Inthis case, the mapping between the different PRS configurations(identified with PRS configuration IDs) and the DRX configurations(identified with DRX cycle IDs) may be provided to the WTRU either by CNfunctions (e.g., AMF, LMF) when supporting CN paging or by RAN whensupporting RAN paging. The mapping between PRS configurations (i.e.assistance information) and DRX configurations may be configured in theWTRU either when the WTRU is in RRC connected mode or aftertransitioning into RRC idle/inactive mode (e.g., via SIB or pagingmessages), for example.

In addition, the WTRU may be assigned WTRU identifiers (e.g.,positioning P-RNTI, positioning I-RNTI) either by the CN or RAN, whichthe WTRU may use to identify the presence of PRS when receiving pagingmessages during paging occasions or to identify presence of pagingmessage when receiving DL PRS. The identifiers assigned to the WTRU maybe either dedicated per-WTRU or per-group, where a group of WTRUs mayuse the common identifier when receiving the PRS during pagingoccasions. In the case of group paging/positioning, a group of WTRUs mayuse the group identifier (e.g., positioning Group-RNTI) for detectingthe presence of the PRS during the paging occasions in DRX cycle whichmay be common to all WTRUs in the group.

While in idle/inactive mode, the WTRU may be triggered to makemeasurements of the PRS based on the detection of the identifierassigned to WTRU and/or the PRS ID during paging occasions of a defaultDRX cycle. For continuing to receive the DL PRS the WTRU may change to adifferent DRX cycle, which may be determined based on the PRSconfiguration ID and the configured mapping between the PRSconfiguration ID and the DRX cycle ID, for example. The WTRU maycontinue making measurements of the received DL PRS withouttransitioning to RRC connected mode based on the assistance informationon the PRS configuration (e.g., measurement duration) available at theWTRU and send to the network the measurement report (e.g., small datatransmission, early data transmission) upon completion of themeasurement duration.

An example of signal flow for positioning during WTRU Idle/Inactive modewith PRS configuration and DRX cycle alignment is shown in FIG. 9 . TheWTRU 201 is initially configured by the RAN with DRX, (920) prior totransitioning into RRC Inactive mode. When triggered by the LMF (922,924), the gNB provides the WTRU with PRS configuration either in SIB, CNpaging or in RAN paging message (926). Upon triggering by aconfiguration alignment event (928) (e.g., DRX configuration is notaligned with PRS config), the WTRU sends an indication to the gNB (RAN)to update DRX config in an initial access (e.g., Msg A)/RNAU message(930). The RAN updates the WTRU's DRX configuration to align with PRSconfig (932). The WTRU receives the updated DRX config in RAN pagingmessage (934). When the gNB receives a Location Request from LMF or DLdata from AMF (936), the gNB pages the WTRU in a CN paging or RAN pagingmessage (938). The WTRU may also receive the PRS in the same timedurations when receiving the paging message. The WTRU measures DL PRS(940) (e.g., during DRX on-duration) and sends the measurement report togNB/LMF in an initial access (e.g., SDT), RNAU message(s) (942). The gNBsends the measurement report to the LMF (944).

WTRU in Idle/Inactive Mode Sends SRSp Based on Triggering Conditions forSending TA/RNA Update Message

In one embodiment, the WTRU in idle/inactive mode sends SRSp for ULpositioning based on triggering conditions for sending TA/RNA updatesmessages. In this case, the WTRU, which may be configured with one ormore associated SRSp configurations (e.g., consisting of different SRSpIDs, resources, power, periodicity), may also be configured with theassociated Tracking Area by the CN or RNA by the RAN. As an example, anSRSp configuration (e.g., SRSp ID X) may be associated with a TrackingArea consisting of at least one cell in cell list A (e.g., cell IDs 1,2,. . . N) and/or an RNA consisting of at least one cell in cell list B(e.g., cell IDs 1,2, . . . M). The cell list configured in the WTRU forTracking Area and/or RNA for the SRSp transmission may be either thesame or a different cell list associated with the Tracking Area and/orRNA configured for idle/inactive mode mobility.

In one embodiment, the WTRU may be triggered to transmit the SRSp basedon one or more of the following conditions:

-   -   Detection of a first cell ID that may be outside of the cell        list associated with the existing/current Tracking Area and/or        RNA configured in the WTRU    -   Detection of a first cell ID that may be inside of the cell list        associated with a different Tracking Area and/or RNA configured        in the WTRU

The WTRU may determine the parameters of the SRSp for UL transmissionbased on the mapping between the SRSp configuration and the associatedcell list in the TA/RNA configured in the WTRU. The WTRU may continuetransmitting the SRSp according to the SRSp configuration until atermination condition is satisfied (e.g., detection of a different cellID inside/outside of the TA/RNA cell list, expiry of timer, reception ofa DL paging message).

An example of signal flow for positioning during WTRU Inactive modemobility for SRS configuration and RNA alignment is shown in FIG. 10 .The WTRU 201 is initially configured by RAN with RNA (1020), prior totransitioning into RRC Inactive mode. When triggered by the LMF (1022),the WTRU is provided with SRS configuration in a RAN paging message(1024). Upon triggering by a positioning mobility event (1026) (e.g.WTRU detects new cell ID outside of RNA), the WTRU transmits SRSp alongwith the RNAU message (1028). Finally, the gNB 203 measures the SRSp(1030) and the gNB sends the measurement report (1032) to the LMF 205.

WTRU in Idle/Inactive Mode Receives Trigger to Update SRSp ConfigurationBased on Configured TA/RNA

In one embodiment, the WTRU may receive a trigger to update the SRSpconfiguration while in idle/inactive mode based on the SRSp transmittedby the WTRU to at least one cell outside of the configured Tracking Areaand/or RNA. Specifically, a WTRU configured for performing UL based orUL+DL based positioning while in idle/inactive mode may use theconfigured resources for sending the SRSp and the WTRU identifier (e.g.,CN assigned ID such as TMSI or RAN assigned ID such as I-RNTI). In thecase when the WTRU approaches a cell boundary or moves into a cell wherethe SRSp sent by the WTRU is not valid or resources are not aligned withthe TA/RNA, the WTRU may receive a paging message from the network forperforming one of the following:

-   -   Update the resources/SRSp configuration: For example, the WTRU        may receive a paging message containing one or more of the        following:        -   A trigger to prohibit using the existing SRSp configuration,            wherein the trigger may contain time/area restrictions            (e.g., timer duration, cell IDs and/or AoDs) for prohibiting            the use of the resources associated with SRSp configurations        -   A change in the SRSp configuration, wherein the request to            change the SRSp may contain the updated SRSp configuration            in the same, first paging message or in a different, second            RAN paging message sent after the first paging message        -   Selection of a different SRSp, wherein the indication to            (re)select SRSp may contain the identifier of a network            selected SRSp configuration from a set of SRSp            pre-configurated in the WTRU    -   Update the TA/RNA: For example, the WTRU may receive in the        paging message either a request to send a TA/RNA update message        or an updated TA/RNA containing the updated cell IDs where the        WTRU may continue using the existing SRSp configuration during        mobility.

FIG. 11 is an example of signal flow for positioning during WTRUInactive mode mobility for trigger-based update for SRS configurationand RNA alignment in accordance with another embodiment. The WTRU 203 isinitially configured by the RAN with RNA (1120), prior to transitioninginto RRC Inactive mode. When triggered by the LMF (1122), the WTRU isprovided with SRSp configuration in a RAN paging message (1124). Upontriggering by an activate SRSp indicator in a RAN paging message (1126),the WTRU transmits SRSp (1128). If triggered by positioning mobility(e.g. SRSp detected at gNBs/TRPs in RAN is different than RNA configuredin WTRU) (1130), the WTRU may be provided with RNA update and/or SRSpconfig update in a RAN paging message (1132), and the WTRU updates itsRNA/SRSp accordingly (1134). Finally, the WTRU transmits the SRSp(1136), which is measured at the gNB 203 (1138), and the measurementreport is sent to the LMF 205 (1140).

WTRU Receives Indication for Using CG Configuration in RRC Inactive/IdleMode during Mobility

In one embodiment, the WTRU may receive a configuration for CG which maybe used when moving to a new cell/gNB, so that the WTRU can continueperforming positioning while remaining in RRC Inactive/idle mode. Forexample, the WTRU may receive the CG configuration from the sourcecell/gNB (e.g., in a RRCRelease message) for sending the positioninginformation and/or measurement reports (e.g., periodically). Along withthe CG configuration, the WTRU may also be configured by the sourcecell/gNB with one or more validity conditions, such as a TA timer, avalidity time duration, and/or a validity area (e.g., cell IDs, possiblyassociated with RNA), which may be verified by the WTRU when using theCG in RRC inactive/idle mode.

In the case, for example, when the WTRU moves to a new cell, where thenew cell ID is within the validity area, the WTRU may continue using theCG configuration for sending positioning information using SDT whileremaining in RRC inactive/idle mode. In the case when one or morevalidity conditions expire, where the WTRU moves to a new/targetcell/gNB which may be outside of the validity area, the WTRU may send inthe RRCResumeRequest message (e.g., in Msg A or Msg 3) wherein the causevalue indicates the expiry and release of the previous CG configurationand/or request for a new CG configuration. The WTRU may include in theRRCResumeRequest the identifier associated with the previous CGconfiguration along with the WTRU identifier (e.g., Inactive-RadioNetwork Temporary Identification (I-RNTI)), for example. When fetchingthe WTRU context from the source cell/gNB, the target cell/gNB maydetermine, based on the identifiers sent by WTRU, whether the WTRU willbe allocated/activated with a new CG configuration or may continue usingthe previous CG configuration. In response to the RRCResumeRequest, theWTRU may receive from the target cell/gNB one or more of the following:

-   -   RRCResume message (e.g., in Msg B or Msg 4) indicating that the        WTRU should use a new CG configuration    -   RRCRelease message (e.g., in Msg B or Msg 4) indicating that the        WTRU should release the previous CG configuration and use a new        CG configuration    -   RRCRelease message indicating that the WTRU should continue        using the previous CG configuration

The RRCResume message and/or RRCRelease message may include theparameters associated with the new CG configuration (e.g., periodicity,time/frequency resources) or may include an activation indication (e.g.,ID of configuration) to activate a preconfigured CG configuration.

WTRU Receives Assistance Data in RRC Inactive/Idle Mode during Mobility

In one embodiment, the WTRU acquires assistance data, which may possiblycontain one or more positioning configurations (e.g., PRS/SRSpconfigurations) when moving to a new cell/gNB while continuing tooperate in RRC inactive/idle mode. The WTRU may initially receive theassistance data, either via broadcast or dedicated RRC signaling, upontriggering of the LPP procedure for positioning while in the coverage ofa source cell/gNB. In this case, the WTRU may receive the assistancedata in dedicated signaling while in RRC Connected mode or whentransitioning to RRC Inactive/idle mode (e.g., in RRCRelease message),for example.

In one example, the WTRU may receive validity conditions (e.g., timer,cell IDs in validity area) associated with the assistance data, whichmay be used to verify the applicability of the assistance data whenmoving to a new cell/gNB and requesting new assistance data. In anotherexample, the WTRU may receive configuration/rules for determiningwhether to send a request for new assistance data in dedicated NAS/RRCsignaling or to acquire the new assistance data via broadcast RRCsignaling (i.e., SIB), possibly including on-demand SIB. For example,the configuration/rules may indicate a first set comprising one or morecell/gNB IDs in which the WTRU may be allowed to send the request fornew assistance data and a second set comprising one or more cell/gNBIDs, which may overlap at least in part with the first set, in which theWTRU may receive the new assistance data in broadcast signaling.

In the case when the conditions/rules associated with sending a requestare satisfied (e.g., the new cell/gNB ID is outside of the validityarea), the WTRU in RRC Inactive/Idle mode may send, in theRRCResumeRequest, the request for new assistance data for one or morenew PRS and/or SRSp configurations. The WTRU may include in theRRCResumeRequest the identifiers associated with the WTRU (e.g., I-RNTI)and the previous assistance data (e.g., PRS/SRSp configuration IDs). Thenew cell/gNB may fetch the WTRU context from the source cell/gNB basedon the WTRU ID and may implicitly determine the request from WTRU for anew assistance data when verifying the release/invalidity of theprevious assistance data from the assistance data ID. Alternatively, theWTRU may include in the RRCResumeRequest the cause value indicating theexpiry and/or release of the previous assistance data/configurations forrequesting the new assistance data. In response to the request, the WTRUmay either receive new assistance data, an activation indication for apreconfigured assistance data (i.e., for preconfigured PRS/SRSpconfiguration), or an indication to continue using the previousassistance data. The WTRU may receive the response indication in anRRCResume message or RRCRelease message (i.e. in Msg B or Msg 4), forexample. In another example, the RRCResume message or RRCRelease messagemay instruct the WTRU to acquire the new assistance data via broadcastRRC signaling.

Minimum Accuracy Requirements and Deferred MT-LR Positioning Examples ofMinimum Accuracy Requirements

The WTRU may receive minimum accuracy or latency requirements from thenetwork (e.g., LMF, gNB) associated with PRS configurations the WTRUreceives from the network. The accuracy and/or latency requirements maybe related to the positioning QoS indicated by higher layers/application(e.g., LCS client) associated with the WTRU, for example. Theminimum/maximum accuracy and/or latency requirements may be at least oneof the following metrics:

-   -   Threshold for standard deviation/variance for the position        estimate made by the WTRU or for measurements made by the WTRU        (e.g., RSRP, TDOA, time of arrival, angle of arrival): For        example, the WTRU may receive a PRS configuration that is        associated with the threshold, indicating that the PRS        configuration can generate a standard deviation/variance below        the threshold.    -   Threshold for the minimum/maximum value for range of the        position estimate or measurements (e.g., RSRP, TDOA, time of        arrival, angle of arrival): For example, the WTRU may receive a        PRS configuration that is associated with the threshold,        indicating that the PRS configuration can generate        minimum/maximum above/below the threshold.    -   Threshold for latency: The WTRU may receive an indication from        the network that the PRS configuration and measurement reporting        configuration satisfies the indicated accuracy requirement. For        example, the WTRU may receive multiple PRS configurations from        the LMF with the number of PRS resources 3, 6 and 9. The WTRU        may receive latency requirements associated with respective        number of resources, 100 ms, 200 ms, 400 ms, indicating that        measurements of 3, 6 and 9 PRS resources yields latency under        100 ms, 200 ms and 400 ms, respectively.    -   Threshold for accuracy: The WTRU may receive multiple PRS        configurations from the network indicating various levels of        accuracy (e.g., order of meters, order of centimeters)        associated with each PRS configuration. For example, the WTRU        may receive two PRS configurations from the network, one        configuration consisting of 6 PRS resources and another        configuration consisting of 20 PRS resources. The WTRU may also        receive configuration associating the configuration with 6 PRS        resources and 20 PRS resources with order of meters and order of        centimeters, respectively, indicating that, by using 20 PRS        resources, the WTRU can achieve centimeter-level accuracy        positioning. Granularity of accuracy is not limited to the one        described in the example. The WTRU may also receive association        of accuracy requirement and different PRS configuration        parameters such as the number of repetitions, number of TRPs        from which the PRS are transmitted from, the number of symbols,        number of repetitions, comb values/factors, bandwidth, muting        pattern, number of PRS resources, PRS resource sets, frequency        layers, etc.

Example Embodiment Using Minimum Accuracy/Latency Requirement

In an embodiment, a WTRU may be configured with one or more PRSconfigurations and/or informed which of the indicated PRS configurationsare able to satisfy the minimum positioning QoS requirements (e.g.accuracy, latency) associated with the positioning service. In anexample, the WTRU may receive the PRS configurations and/or theassociated identifiers in a first indication (e.g., in LPP assistancedata or SIB), followed by a second indication containing information onwhich of the PRS configurations (e.g., IDs/flags) are able to satisfythe minimum accuracy (and/or latency) requirement. In another example,the WTRU may receive, in the same message (e.g. assistance data), thePRS configurations and indications indicating which of the PRSconfigurations (e.g., IDs/flags) satisfy the minimum accuracy (and/orlatency) requirement. In another example, the WTRU may determine whichof the (pre)configured PRS configurations provided to the WTRU are ableto satisfy the minimum accuracy requirement based on comparison of themeasurements made and/or calculation of the positioning information withrespect to the positioning information determined using one or moreother reference positioning methods (e.g., GNSS positioning).

In one embodiment, when the WTRU may operate either in RRC CONNECTED orRRC INACTIVE state, the WTRU may select from the preconfigured one ormore PRS configurations received from the network (e.g., LMF and/orgNB), a PRS configuration to use for measurements based on at leastwhether the selected PRS configuration is able to satisfy the minimumaccuracy requirement associated with the positioning service of theWTRU. Other criterion used by the WTRU for selecting a PRS configurationmay include the data volume threshold configured by the network (e.g.,gNB) when the WTRU is configured with SDT for sending data in UL whileoperating in INACTIVE state, for example. In this case, the WTRU may be(pre)configured with one or more PRS configurations, where the differentPRS configurations may include measurement configurations (e.g., PRSresources used for making measurements) and/or reporting configurations(e.g., information on which of the measurements to be reported). Forexample, the reporting configuration may indicate whether to report theabsolute values of the measurements made on each of the N resources,average values of the measurements made upon averaging over the N numberof resources, selected measurement values where the selection is made onthe basis of measurements which are higher/lower than a configuredthreshold, etc. The different reporting configurations may result indifferent payload sizes when sending the measurement report in theuplink to the network. The (expected) payload sizes of the measurementreport associated with the reporting configurations may be indicated bythe network to the WTRU (e.g., in assistance data) or determined by theWTRU based on estimation of the number of resulting bits in ameasurement report prior to or after performing the measurements.

Upon receiving the PRS configurations (i.e., measurement configurationand/or reporting configuration) as well as the configuration for SDT(e.g., data volume threshold) for use during INACTIVE state operation,the WTRU may select a PRS configuration such that the selectedconfiguration satisfies the minimum accuracy requirement and/or theresulting payload size of the measurement report is less than or equalto the data volume threshold associated with the resources configuredfor SDT (e.g., RACH/CG). On the condition that at least one of the PRSconfigurations received from the network is able to satisfy the minimumaccuracy (and/or latency) requirement and results in a measurementreport the payload size of which is less than or equal to the SDT datavolume threshold, the WTRU may select a PRS configuration from the(pre)configurations for performing the measurements. In this case, theWTRU may select a PRS configuration such that the resulting differencebetween the payload size of the measurement report and the configureddata volume threshold is minimized, for example.

Upon selecting such PRS configuration, the WTRU may perform measurementson the PRS and may send the measurement report to the network usingresources (e.g., RACH and/or CG) configured for SDT while in INACTIVEstate, for example. In an example, the WTRU may include along with themeasurement report sent to the network (e.g., the LMF), informationrelated to the selected PRS configuration and/or the data volumethreshold configured for use with SDT. Alternatively, on the conditionthat none of the (pre)configured PRS configurations are able to satisfythe minimum accuracy (and/or latency) requirement and/or results in ameasurement report the payload size of which is less than or equal tothe SDT data volume threshold, the WTRU may send an indication to thegNB (e.g., in a RRCResumeRequest message) requesting to transition theWTRU to RRC CONNECTED state. This would enable for the WTRU to performmeasurements using a suitable PRS configuration (e.g., a PRSconfiguration that satisfies minimum accuracy/latency requirements) andsend the measurement report to the network when operating in CONNECTEDstate.

The aforementioned example embodiment, including the procedure for theWTRU to perform positioning measurements and reporting in INACTIVEand/or CONNECTED state based on accuracy requirement and SDT data volumethreshold is illustrated in FIG. 13 . More particularly, at step 1, theWTRU receives (e.g., from the LMF) one or more PRS configurations,including a measurement configuration and a measurement reportingconfiguration. The WTRU also may receive an indication of which ones ofthe various configurations satisfy which minimum accuracy requirements.Optionally, at step 2, the WTRU may send to the serving gNB ameasurement report, which may include payload sized for PRSconfigurations. At step 3, the serving gNB may send to the WTRU a SDTconfiguration, including a data volume threshold.

Next, at step 4, the WTRU may eventually go to INACTIVE state (e.g., dueto data inactivity). While in INACTIVE state, the WTRU determines, atstep 5, whether any PRS configurations satisfy the minimum accuracyrequirements and have a payload size that is less than the establisheddata volume threshold. IF either of those conditions are not met, theWTRU will seek to go back to CONNECTED state so that it can performmeasurements and/or report its measurements to the network (step 6 b).If, on the other hand, both conditions are met, then the WTRU remains inINACTIVE state to perform the measurements and/or report them to thenetwork (Step 6 a). Specifically, in an embodiment, the WTRU selects aPRS configuration with a payload size closest to, but smaller than theSDT data volume threshold from the ones satisfying the minimum accuracyrequirement, performs the measurement according to the selectedconfiguration and sends the measurement report to the LMF using SDT. Thereport may include the measurement information as well as an indicationof the selected PRS configuration and SDT data volume threshold.

In this embodiment, a WTRU may be configured to receive (e.g., from anLMF) assistance data including one or more PRS configurations (eachincluding a measurement config and a measurement report config), whereat least some of the PRS configurations are indicated to meet a minimumaccuracy requirement. The WTRU may send an indication (to a gNB) of thepayload sizes (of the measurement report) associated with the one ormore PRS configurations (payload sizes are WTRU determined or LMFindicated). The WTRU may receive a small data transmission (SDT) config(from the gNB) including a data volume threshold (DVT) for SDT(indicating the maximum payload size for SDT). In an example, when atleast one PRS configuration from the one or more received PRSconfigurations indicated to satisfy the minimum accuracy requirement hasan associated payload size less than the DVT for SDT: the WTRU mayselect a PRS config with an associated payload size closest to the DVTfor SDT from among the at least one PRS configurations that satisfy theminimum accuracy requirement, and perform PRS measurements and send ameasurement report (e.g., to the LMF) based on the selected PRS configusing an SDT (in INACTIVE state), where the measurement report indicatesthe selected PRS config and the DVT for SDT. In another example, whennone of the PRS configurations indicated to satisfy the minimum accuracyrequirement have an associated payload size less than the DVT for SDT,the WTRU may send a connection request (to the gNB) (e.g., to transitionto CONNECTED state to be able to send a measurement report).

Deferred MT-LR Positioning in INACTIVE State

In one embodiment, a WTRU may perform positioning related actions,including selection of PRS configuration, performing measurements onDL-PRS and transmission of measurement reports/location estimates, whileoperating in INACTIVE state when triggered by one or more eventsconfigured by a deferred MT-LR positioning procedure. The deferred MT-LRpositioning refers to a procedure where the higher layers/application(e.g., LCS client), possibly located in the network, may establish andconfigure a location service session (e.g., LPP session) involving theLMF, AMF, and WTRU. In this case, upon receiving the deferred MT-LRrequest from the higher layers/application, the WTRU may be configuredwith PRS configuration(s) and one or more triggering events for the WTRUto monitor and perform measurements using the PRS configuration(s). Forexample, when a triggering event is detected by the WTRU, the WTRUperforms the measurements and sends the measurement report (e.g., forWTRU-assisted mode) or location estimate (e.g. for WTRU-based mode) tothe LMF. The LMF then sends the location information of the WTRU to thehigher layers/application. The deferred MT-LR procedure is typicallyconfigured for use when the WTRU may operate in RRC CONNECTED state,where the positioning procedures (e.g., LPP procedures) related to WTRUreceiving assistance data (e.g., consisting of PRS configuration),performing measurements and sending measurement reports may be donewithout consideration of any low power operation and any limitation interms of payload size that can be supported for transmission ofmeasurement reports.

For supporting deferred MT-LR in INACTIVE/IDLE mode, the WTRU should beable to perform one or more positioning related actions before, during,or after being triggered by the configured event(s). When performing thepositioning related actions, including measurements and transmission ofmeasurement reports/location estimates when detecting a triggeringevent, the WTRU may use one or more of the (pre)configured PRSconfigurations, for example. The (pre)configured PRS configurationsreceived by the WTRU may include one or more aperiodic, periodic, and/orsemi-persistent PRS configurations, where the use of differentconfigurations for measurements may result in achieving differentpositioning QoS (e.g., accuracy, latency), for example. In this case,the PRS configurations may be received by the WTRU when in CONNECTEDstate, while the detection of a triggering event and the performing ofpositioning related actions may be done upon transitioning to INACTIVEstate. For example, the triggering events configured in the WTRU fordeferred MT-LR may include one or more of the following:

-   -   Time/temporal event: the WTRU may perform measurements at the        start/expiry of a temporal event (e.g., start/expiry of a timer        with a configured duration). For a fixed configured time        duration, the WTRU performs measurements periodically with a        periodicity that is a function of the time duration, for        example.    -   Area/mobility event: the WTRU may perform measurements when        detecting one or more configured cell IDs during mobility. In        this case, the WTRU may perform measurements and send the        measurement reports when entering the coverage area comprising        at least one new cell, for example.    -   End of data/control channel reception: the WTRU may perform        measurements when reception of PDCCH or PDSCH is completed        during INACTIVE state. The WTRU may receive an indication from        the network of PDCCH or PDSCH (e.g., DCI) the WTRU may receive.        After receiving the indicated PDCCH or PDSCH, the WTRU should        perform measurements of PRS.

In one embodiment related to INACTIVE/IDLE mode operation, the WTRU mayassociate the detection of one or more triggering events with theselection of a (pre)configured PRS configuration such that measurementsperformed in INACTIVE/IDLE mode and the determined WTRU locationinformation results in satisfying a positioning QoS requirement (e.g.,accuracy, latency) associated with deferred MT-LR. In an example, theWTRU may be configured with one or more triggering events, possibly whenreceiving a set of PRS configurations (e.g., in LPP assistance data).When transitioning to INACTIVE state, the WTRU may be configured by thegNB with one or more data volume threshold values associated with thepayload sizes of data to be sent in the uplink using resources (e.g.,RACH/CG) related to SDT configuration. When operating in INACTIVE state,the WTRU may select a PRS configuration upon detecting a triggeringevent, where the selection of the PRS configuration may be based ondifferent factors including data volume threshold of measurement reportpayload size, the positioning QoS requirement (e.g., minimumaccuracy/latency), and/or type of the detected triggering event (e.g.,temporal, mobility). For example, the WTRU may select a PRSconfiguration such that the resulting payload size of the measurementreport is less than the data volume threshold, satisfies the minimumaccuracy requirement for deferred MT-LR, and/or corresponds to the typeof triggering event. Upon performing measurements using the selected PRSconfiguration, the WTRU may send the measurement report using resourcesconfigured for SDT where the measurement report may include informationon the selected PRS configuration, the size of data volume threshold,and/or type of triggering event detected, for example.

The WTRU Reporting Subset of Measurements During INACTIVE ModePositioning Smaller Number of Quantities to Report

To reduce the volume of measurement reports during INACTIVE mode, theWTRU may be configured by the network (e.g., LMF or gNB) to report asubset of measurements that the WTRU made during RRC_CONNECTED. Forexample, if the WTRU is configured to report measurements up to M PRSresources during RRC_CONNECTED, the WTRU may be configured by thenetwork to report up to N PRS resources where N<M. In another example,the WTRU may be configured to report at reduced resolution/granularityof measurements or number of measurements for at least one of thefollowing measurement/parameters during INACTIVE mode positioning:

-   -   Number of paths in multipath channels    -   Number of PRS resources    -   Resolution/granularity of RSRP    -   Resolution/granularity of time of arrival, TDOA, RSTD    -   Resolution/granularity of Rx-Tx time difference    -   Resolution/granularity of angle of arrival, angle of departure

Reduced Frequency for Reporting

In another example, the WTRU may be configured to report measurementreports at different periodicities. The WTRU may be configured with asmaller number of measurement report occasions (e.g., longer intervalsbetween reports) compared to the number of occasions when the WTRU is inCONNECTED mode. For example, the WTRU may be configured with adecimation/muting pattern (e.g., expressed in a bitmap pattern) whichindicates which measurement occasion the WTRU should skip or reportduring INACTIVE mode. For example, during CONNECTED mode, the WTRU maybe configured to report every 1 ms. However, the WTRU may be configuredto report every 10th occasion when the WTRU is in INACTIVE mode ascompared to the reporting occasions during CONNECTED mode. Thus, theWTRU may report every 10 ms when the WTRU transitions to INACTIVE mode.The configuration of the reporting occasions for INACTIVE mode may besent to the WTRU when the WTRU is in CONNECTED mode. Once the WTRUtransitions to CONNECTED mode from INACTIVE mode, the WTRU may revert tothe reporting configuration it had during CONNECTED mode (i.e., every 1ms).

In another example, the WTRU may be configured (e.g., while in CONNECTEDmode) with the number of measurement reports the WTRU needs to send tothe network. For instance, the WTRU may be configured to send Nmeasurement reports while the WTRU is in INACTIVE mode. After the WTRUsends the N measurement reports, the WTRU may send an indication to thenetwork requesting more positioning occasions. Alternatively, the WTRUmay terminate positioning after the WTRU sends N measurement reports tothe network. In another example, the WTRU may be configured to keepsending the measurement reports at a configured periodicity while theWTRU is in INACTIVE mode until the WTRU transitions into CONNECTED mode.

Determining and Transmitting Positioning Information

In one embodiment, a method implemented in a WTRU of reportingpositioning information to a network comprising receiving an indicationfrom the network while in a low power connectivity state to commencepositioning reporting; responsive to the indication, conductingpositioning measurements while remaining in the low power connectivitystate; and transmitting a positioning report to the network. In anexample, the indication is received in a RACH procedure. The low powerconnectivity state may be one of RRC idle mode and RRC inactive mode. Inan example, responsive to the indication from the network, the methodmay include: 1) transmitting a request to transition to RRC_CONNECTEDmode; or 2) transmitting a signal to the network indicating a capabilityof the WTRU to perform positioning reporting while in the low powerconnectivity state.

In an example, the indication from the network includes a positioningreporting configuration for the WTRU.

In an example, the method may include transmitting a request to thenetwork for a configuration for positioning measurement and/or reportingwhile in the low power connectivity state.

In an example, the WTRU may partitions the positioning report into aplurality of separate messages.

In an example, the method may include configuring a data volumethreshold value for at least one Signaling Radio Bearer (SRB), andtransmitting the measurement report in a Small Data Transmission (SDT)on the at least one SRB configured with a data volume threshold when avolume of the measurement report is less than the configured data volumethreshold for that SRB. In some cases, the method may include receivinga data volume threshold configuration from an LMF of the network.

In an example, the method may include transmitting to the networkinformation indicating a size of the measurement data to be transmitted.The information indicating the size of the measurement data to betransmitted may be transmitted in any one of a radio resource control(RRC) message, Media Access Control (MAC) Control Element (CE), orUplink Control Information (UCI).

In an example, the method may include dynamically reconfiguring the datavolume threshold for the at least one SRB. The dynamicallyreconfiguration of the data volume threshold for the at least one SRBmay comprises: determining that the size of the measurement data to betransmitted exceeds a default data volume threshold of the applicableSRB and is less than a second data volume threshold of the applicableSRB greater than the default threshold; responsive to the determination,transmitting a resume request to the network containing an indicatorassociated with the second data volume threshold.

In an example, the method may include determining that the size of themeasurement data to be transmitted exceeds a data volume threshold, andin response to the determination, segmenting the measurement data intosegments smaller than the data volume threshold and transmitting thedata in the segments.

In an example, the method may include determining an amount ofmeasurement data to be transmitted to the network based on the datavolume threshold.

In an example, the method may include receiving from the network anindication of at least one Positioning Reference Signal (PRS)configuration, including a configuration for taking measurements and aconfiguration for reporting measurements to the network; receiving fromthe network an indication of a level of positioning determinationquality satisfied by each PRS configuration; and selecting a PRSconfiguration to use while in a low power connectivity state based onsatisfaction of a minimum positioning accuracy threshold and a maximummeasurement payload size threshold. The indication of level ofpositioning determination quality satisfied by each PRS configurationmay include at least one of an accuracy of the positioning determinationand a latency of the positioning determination. The PRS configurationmay be determined/selected based on a criterion to minimize a differencebetween a payload size of the measurement report and maximum payloadsize requirement.

In some examples, if the WTRU does not have a PRS configuration thatsatisfies the minimum positioning accuracy threshold and the maximummeasurement payload size threshold, the WTRU may transmit a request tothe network to transition to CONNECTED mode.

In some examples, the indication of level of positioning determinationquality comprises at least one of: a threshold for standarddeviation/variance for the position estimate; a threshold for a range ofthe position estimate; a threshold for latency; and/or a threshold foraccuracy.

In one embodiment, a method implemented in a WTRU of reportingpositioning information to a network comprising: receiving assistancedata including one or more Positioning Reference Signal (PRS)configurations (each may include a measurement config and a measurementreport config), wherein at least one of the PRS configurations areindicated to meet a minimum accuracy requirement; sending an indication(e.g., to a gNB) of the payload sizes (of measurement report(s))associated with the one or more PRS configurations; receiving a smalldata transmission (SDT) configuration (e.g., from the gNB) including adata volume threshold (DVT) for SDT (e.g., indicating the maximumpayload size for SDT); on condition that at least one PRS config fromthe one or more received PRS configurations indicated to satisfy theminimum accuracy requirement has an associated payload size less thanthe DVT for SDT: selecting a PRS config with an associated payload sizeclosest to the DVT for SDT from among the at least one PRSconfigurations that satisfy the minimum accuracy requirement; andperforming PRS measurements and sending a measurement report (to theLMF) based on the selected PRS config using an SDT (e.g., in INACTIVEstate), wherein the measurement report indicates the selected PRS configand the DVT for SDT; and on condition that none of the PRSconfigurations indicated to satisfy the minimum accuracy requirementhave an associated payload size less than the DVT for SDT, sending aconnection request (e.g., to the gNB) (e.g., to transition to CONNECTEDstate to be able to send a measurement report).

REFERENCES

The following references may have been referred to hereinabove and areincorporated in full herein by reference: [1] 3GPP, “User Equipment (UE)positioning in NG-RAN,” TS 38.305, ver. 16.1.0, July 2020; and [2] 3GPP,“Radio Resource Control (RRC) protocol specification,” TS 38.331, ver.16.1.0, July 2020.

CONCLUSION

Although features and elements are described above in particularcombinations, one of ordinary skill in the art will appreciate that eachfeature or element can be used alone or in any combination with theother features and elements. In addition, the methods described hereinmay be implemented in a computer program, software, or firmwareincorporated in a computer readable medium for execution by a computeror processor. Examples of non-transitory computer-readable storage mediainclude, but are not limited to, a read only memory (ROM), random accessmemory (RAM), a register, cache memory, semiconductor memory devices,magnetic media such as internal hard disks and removable disks,magneto-optical media, and optical media such as CD-ROM disks, anddigital versatile disks (DVDs). A processor in association with softwaremay be used to implement a radio frequency transceiver for use in a WTRU102, WTRU, terminal, base station, RNC, or any host computer.

Moreover, in the embodiments described above, processing platforms,computing systems, controllers, and other devices containing processorsare noted. These devices may contain at least one Central ProcessingUnit (“CPU”) and memory. In accordance with the practices of personsskilled in the art of computer programming, reference to acts andsymbolic representations of operations or instructions may be performedby the various CPUs and memories. Such acts and operations orinstructions may be referred to as being “executed,” “computer executed”or “CPU executed.”

One of ordinary skill in the art will appreciate that the acts andsymbolically represented operations or instructions include themanipulation of electrical signals by the CPU. An electrical systemrepresents data bits that can cause a resulting transformation orreduction of the electrical signals and the maintenance of data bits atmemory locations in a memory system to thereby reconfigure or otherwisealter the CPU's operation, as well as other processing of signals. Thememory locations where data bits are maintained are physical locationsthat have particular electrical, magnetic, optical, or organicproperties corresponding to or representative of the data bits. Itshould be understood that the exemplary embodiments are not limited tothe above-mentioned platforms or CPUs and that other platforms and CPUsmay support the provided methods.

The data bits may also be maintained on a computer readable mediumincluding magnetic disks, optical disks, and any other volatile (e.g.,Random Access Memory (“RAM”)) or non-volatile (e.g., Read-Only Memory(“ROM”)) mass storage system readable by the CPU. The computer readablemedium may include cooperating or interconnected computer readablemedium, which exist exclusively on the processing system or aredistributed among multiple interconnected processing systems that may belocal or remote to the processing system. It is understood that therepresentative embodiments are not limited to the above-mentionedmemories and that other platforms and memories may support the describedmethods.

In an illustrative embodiment, any of the operations, processes, etc.described herein may be implemented as computer-readable instructionsstored on a computer-readable medium. The computer-readable instructionsmay be executed by a processor of a mobile unit, a network element,and/or any other computing device.

There is little distinction left between hardware and softwareimplementations of aspects of systems. The use of hardware or softwareis generally (but not always, in that in certain contexts the choicebetween hardware and software may become significant) a design choicerepresenting cost vs. efficiency tradeoffs. There may be variousvehicles by which processes and/or systems and/or other technologiesdescribed herein may be affected (e.g., hardware, software, and/orfirmware), and the preferred vehicle may vary with the context in whichthe processes and/or systems and/or other technologies are deployed. Forexample, if an implementer determines that speed and accuracy areparamount, the implementer may opt for a mainly hardware and/or firmwarevehicle. If flexibility is paramount, the implementer may opt for amainly software implementation. Alternatively, the implementer may optfor some combination of hardware, software, and/or firmware.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes via the use of block diagrams, flowcharts,and/or examples. Insofar as such block diagrams, flowcharts, and/orexamples contain one or more functions and/or operations, it will beunderstood by those within the art that each function and/or operationwithin such block diagrams, flowcharts, or examples may be implemented,individually and/or collectively, by a wide range of hardware, software,firmware, or virtually any combination th ereof. Suitable processorsinclude, by way of example, a general purpose processor, a specialpurpose processor, a conventional processor, a digital signal processor(DSP), a plurality of microprocessors, one or more microprocessors inassociation with a DSP core, a controller, a microcontroller,Application Specific Integrated Circuits (ASICs), Application SpecificStandard Products (ASSPs); Field Programmable Gate Arrays (FPGAs)circuits, any other type of integrated circuit (IC), and/or a statemachine.

Although features and elements are provided above in particularcombinations, one of ordinary skill in the art will appreciate that eachfeature or element can be used alone or in any combination with theother features and elements. The present disclosure is not to be limitedin terms of the particular embodiments described in this application,which are intended as illustrations of various aspects. Manymodifications and variations may be made without departing from itsspirit and scope, as will be apparent to those skilled in the art. Noelement, act, or instruction used in the description of the presentapplication should be construed as critical or essential to theinvention unless explicitly provided as such. Functionally equivalentmethods and apparatuses within the scope of the disclosure, in additionto those enumerated herein, will be apparent to those skilled in the artfrom the foregoing descriptions. Such modifications and variations areintended to fall within the scope of the appended claims. The presentdisclosure is to be limited only by the terms of the appended claims,along with the full scope of equivalents to which such claims areentitled. It is to be understood that this disclosure is not limited toparticular methods or systems.

It is also to be understood that the terminology used herein is for thepurpose of describing particular embodiments only, and is not intendedto be limiting. As used herein, when referred to herein, the terms“station” and its abbreviation “STA”, “user equipment” and itsabbreviation “UE” may mean (i) a wireless transmit and/or receive unit(WTRU), such as described infra; (ii) any of a number of embodiments ofa WTRU, such as described infra; (iii) a wireless-capable and/orwired-capable (e.g., tetherable) device configured with, inter alia,some or all structures and functionality of a WTRU, such as describedinfra; (iii) a wireless-capable and/or wired-capable device configuredwith less than all structures and functionality of a WTRU, such asdescribed infra; or (iv) the like. Details of an example WTRU, which maybe representative of any WTRU recited herein, are provided herein withrespect to FIGS. 1A-1D.

In certain representative embodiments, several portions of the subjectmatter described herein may be implemented via Application SpecificIntegrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs),digital signal processors (DSPs), and/or other integrated formats.However, those skilled in the art will recognize that some aspects ofthe embodiments disclosed herein, in whole or in part, may beequivalently implemented in integrated circuits, as one or more computerprograms running on one or more computers (e.g., as one or more programsrunning on one or more computer systems), as one or more programsrunning on one or more processors (e.g., as one or more programs runningon one or more microprocessors), as firmware, or as virtually anycombination thereof, and that designing the circuitry and/or writing thecode for the software and or firmware would be well within the skill ofone of skill in the art in light of this disclosure. In addition, thoseskilled in the art will appreciate that the mechanisms of the subjectmatter described herein may be distributed as a program product in avariety of forms, and that an illustrative embodiment of the subjectmatter described herein applies regardless of the particular type ofsignal bearing medium used to actually carry out the distribution.Examples of a signal bearing medium include, but are not limited to, thefollowing: a recordable type of medium such as a floppy disk, a harddisk drive, a CD, a DVD, a digital tape, a computer memory, etc., and atransmission type medium such as a digital and/or an analogcommunication medium (e.g., a fiber optic cable, a waveguide, a wiredcommunications link, a wireless communication link, etc.).

The herein described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely examples, and that in fact many other architectures may beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality may beachieved. Hence, any two components herein combined to achieve aparticular functionality may be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermediate components. Likewise, any two componentsso associated may also be viewed as being “operably connected”, or“operably coupled”, to each other to achieve the desired functionality,and any two components capable of being so associated may also be viewedas being “operably couplable” to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents and/or wirelessly interactable and/or wirelessly interactingcomponents and/or logically interacting and/or logically interactablecomponents.

With respect to the use of substantially any plural and/or singularterms herein, those having skill in the art can translate from theplural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations may be expressly set forth herein for sakeof clarity.

It will be understood by those within the art that, in general, termsused herein, and especially in the appended claims (e.g., bodies of theappended claims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.). It will be further understood by those within the art that if aspecific number of an introduced claim recitation is intended, such anintent will be explicitly recited in the claim, and in the absence ofsuch recitation no such intent is present. For example, where only oneitem is intended, the term “single” or similar language may be used. Asan aid to understanding, the following appended claims and/or thedescriptions herein may contain usage of the introductory phrases “atleast one” and “one or more” to introduce claim recitations. However,the use of such phrases should not be construed to imply that theintroduction of a claim recitation by the indefinite articles “a” or“an” limits any particular claim containing such introduced claimrecitation to embodiments containing only one such recitation, even whenthe same claim includes the introductory phrases “one or more” or “atleast one” and indefinite articles such as “a” or “an” (e.g., “a” and/or“an” should be interpreted to mean “at least one” or “one or more”). Thesame holds true for the use of definite articles used to introduce claimrecitations. In addition, even if a specific number of an introducedclaim recitation is explicitly recited, those skilled in the art willrecognize that such recitation should be interpreted to mean at leastthe recited number (e.g., the bare recitation of “two recitations,”without other modifiers, means at least two recitations, or two or morerecitations). Furthermore, in those instances where a conventionanalogous to “at least one of A, B, and C, etc.” is used, in generalsuch a construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, and C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). In those instances where aconvention analogous to “at least one of A, B, or C, etc.” is used, ingeneral such a construction is intended in the sense one having skill inthe art would understand the convention (e.g., “a system having at leastone of A, B, or C” would include but not be limited to systems that haveA alone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). It will be furtherunderstood by those within the art that virtually any disjunctive wordand/or phrase presenting two or more alternative terms, whether in thedescription, claims, or drawings, should be understood to contemplatethe possibilities of including one of the terms, either of the terms, orboth terms. For example, the phrase “A or B” will be understood toinclude the possibilities of “A” or “B” or “A and B.” Further, the terms“any of” followed by a listing of a plurality of items and/or aplurality of categories of items, as used herein, are intended toinclude “any of,” “any combination of,” “any multiple of,” and/or “anycombination of multiples of” the items and/or the categories of items,individually or in conjunction with other items and/or other categoriesof items. Moreover, as used herein, the term “set” or “group” isintended to include any number of items, including zero. Additionally,as used herein, the term “number” is intended to include any number,including zero.

In addition, where features or aspects of the disclosure are describedin terms of Markush groups, those skilled in the art will recognize thatthe disclosure is also thereby described in terms of any individualmember or subgroup of members of the Markush group.

As will be understood by one skilled in the art, for any and allpurposes, such as in terms of providing a written description, allranges disclosed herein also encompass any and all possible subrangesand combinations of subranges thereof. Any listed range can be easilyrecognized as sufficiently describing and enabling the same range beingbroken down into at least equal halves, thirds, quarters, fifths,tenths, etc. As a non-limiting example, each range discussed herein maybe readily broken down into a lower third, middle third and upper third,etc. As will also be understood by one skilled in the art all languagesuch as “up to,” “at least,” “greater than,” “less than,” and the likeincludes the number recited and refers to ranges which can besubsequently broken down into subranges as discussed above. Finally, aswill be understood by one skilled in the art, a range includes eachindividual member. Thus, for example, a group having 1-3 cells refers togroups having 1, 2, or 3 cells. Similarly, a group having 1-5 cellsrefers to groups having 1, 2, 3, 4, or 5 cells, and so forth.

Moreover, the claims should not be read as limited to the provided orderor elements unless stated to that effect. In addition, use of the terms“means for” in any claim is intended to invoke 35 U.S.C. § 112, ¶ 6 ormeans-plus-function claim format, and any claim without the terms “meansfor” is not so intended.

Although the invention is illustrated and described herein withreference to specific embodiments, the invention is not intended to belimited to the details shown. Rather, various modifications may be madein the details within the scope and range of equivalents of the claimsand without departing from the invention.

Throughout the disclosure, one of skill understands that certainrepresentative embodiments may be used in the alternative or incombination with other representative embodiments.

Although features and elements are described above in particularcombinations, one of ordinary skill in the art will appreciate that eachfeature or element can be used alone or in any combination with theother features and elements. In addition, the methods described hereinmay be implemented in a computer program, software, or firmwareincorporated in a computer readable medium for execution by a computeror processor. Examples of non-transitory computer-readable storage mediainclude, but are not limited to, a read only memory (ROM), random accessmemory (RAM), a register, cache memory, semiconductor memory devices,magnetic media such as internal hard disks and removable disks,magneto-optical media, and optical media such as CD-ROM disks, anddigital versatile disks (DVDs). A processor in association with softwaremay be used to implement a radio frequency transceiver for use in a UE,WTRU, terminal, base station, RNC, or any host computer.

Moreover, in the embodiments described above, processing platforms,computing systems, controllers, and other devices containing processorsare noted. These devices may contain at least one Central ProcessingUnit (“CPU”) and memory. In accordance with the practices of personsskilled in the art of computer programming, reference to acts andsymbolic representations of operations or instructions may be performedby the various CPUs and memories. Such acts and operations orinstructions may be referred to as being “executed,” “computer executed”or “CPU executed.”

One of ordinary skill in the art will appreciate that the acts andsymbolically represented operations or instructions include themanipulation of electrical signals by the CPU. An electrical systemrepresents data bits that can cause a resulting transformation orreduction of the electrical signals and the maintenance of data bits atmemory locations in a memory system to thereby reconfigure or otherwisealter the CPU's operation, as well as other processing of signals. Thememory locations where data bits are maintained are physical locationsthat have particular electrical, magnetic, optical, or organicproperties corresponding to or representative of the data bits.

The data bits may also be maintained on a computer readable mediumincluding magnetic disks, optical disks, and any other volatile (e.g.,Random Access Memory (“RAM”)) or non-volatile (“e.g., Read-Only Memory(“ROM”)) mass storage system readable by the CPU. The computer readablemedium may include cooperating or interconnected computer readablemedium, which exist exclusively on the processing system or aredistributed among multiple interconnected processing systems that may belocal or remote to the processing system. It is understood that therepresentative embodiments are not limited to the above-mentionedmemories and that other platforms and memories may support the describedmethods.

No element, act, or instruction used in the description of the presentapplication should be construed as critical or essential to theinvention unless explicitly described as such. In addition, as usedherein, the article “a” is intended to include one or more items. Whereonly one item is intended, the term “one” or similar language is used.Further, the terms “any of” followed by a listing of a plurality ofitems and/or a plurality of categories of items, as used herein, areintended to include “any of,” “any combination of,” “any multiple of,”and/or “any combination of multiples of” the items and/or the categoriesof items, individually or in conjunction with other items and/or othercategories of items. Further, as used herein, the term “set” is intendedto include any number of items, including zero. Further, as used herein,the term “number” is intended to include any number, including zero.

Moreover, the claims should not be read as limited to the describedorder or elements unless stated to that effect. In addition, use of theterm “means” in any claim is intended to invoke 35 U.S.C. § 112, ¶ 6,and any claim without the word “means” is not so intended.

Suitable processors include, by way of example, a general purposeprocessor, a special purpose processor, a conventional processor, adigital signal processor (DSP), a plurality of microprocessors, one ormore microprocessors in association with a DSP core, a controller, amicrocontroller, Application Specific Integrated Circuits (ASICs),Application Specific Standard Products (ASSPs); Field Programmable GateArrays (FPGAs) circuits, any other type of integrated circuit (IC),and/or a state machine.

A processor in association with software may be used to implement aradio frequency transceiver for use in a wireless transmit receive unit(WTRU), user equipment (UE), terminal, base station, Mobility ManagementEntity (MME) or Evolved Packet Core (EPC), or any host computer. TheWTRU may be used m conjunction with modules, implemented in hardwareand/or software including a Software Defined Radio (SDR), and othercomponents such as a camera, a video camera module, a videophone, aspeakerphone, a vibration device, a speaker, a microphone, a televisiontransceiver, a hands free headset, a keyboard, a Bluetooth® module, afrequency modulated (FM) radio unit, a Near Field Communication (NFC)Module, a liquid crystal display (LCD) display unit, an organiclight-emitting diode (OLED) display unit, a digital music player, amedia player, a video game player module, an Internet browser, and/orany Wireless Local Area Network (WLAN) or Ultra Wide Band (UWB) module.

Although the invention has been described in terms of communicationsystems, it is contemplated that the systems may be implemented insoftware on microprocessors/general purpose computers (not shown). Incertain embodiments, one or more of the functions of the variouscomponents may be implemented in software that controls ageneral-purpose computer.

In addition, although the invention is illustrated and described hereinwith reference to specific embodiments, the invention is not intended tobe limited to the details shown. Rather, various modifications may bemade in the details within the scope and range of equivalents of theclaims and without departing from the invention.

What is claimed is:
 1. A method implemented in a wirelesstransmit/receive unit (WTRU), the method comprising: receivingconfiguration information indicating 1) a set of positioningconfigurations, and 2) a threshold associated with a data volume of adata transmission; selecting, from the set of positioningconfigurations, a positioning configuration associated with a payloadsize being less than threshold; and sending a measurement reportindicating the selected positioning configuration and a positioningmeasurement performed using the selected positioning configuration. 2.The method of claim 1, further comprising: determining, based on theconfiguration information, that each of the set of positioningconfigurations is 1) associated with a respective payload size beingequal to or more than the threshold or 2) does not satisfy a positioningrequirement; and sending a connection request requesting a transitionfrom a low-power connectivity mode to a connected mode to performpositioning measurement and measurement reporting.
 3. (canceled)
 4. Themethod of claim 1, wherein the set of positioning configurationscomprises a set of positioning reference signal (PRS) configurations,and wherein the positioning configuration is selected from a subset ofthe set of PRS configurations.
 5. (canceled)
 6. The method of claim 1,wherein each of the set of positioning configurations comprises at leastone of a respective measurement configuration or a respectivemeasurement report configuration.
 7. The method of claim 1, furthercomprising: sending an indication indicating a set of payload sizes,wherein each payload size of the set of payload sizes is associated witha respective positioning configuration of the set of positioningconfigurations.
 8. (canceled)
 9. The method of claim 1, wherein themeasurement report comprises information indicating the thresholdassociated with the data volume of the data transmission. 10-12.(canceled)
 13. The method of claim 1, wherein the threshold is a maximumpayload size for a small data transmission (SDT). 14-18. (canceled) 19.A wireless transmit/receive unit (WTRU) comprising: a receiverconfigured to receive configuration information indicating 1) a set ofpositioning configurations and 2) a threshold associated with a datavolume of a data transmission; a processor configured to select, fromthe set of positioning configurations, a positioning configurationassociated with a payload size being less than the threshold; and atransmitter configured to send a measurement report indicating theselected positioning configuration and a positioning measurementperformed using the selected positioning configuration.
 20. (canceled)21. The WTRU of claim 19, wherein the threshold is a data volumethreshold (DVT), the data transmission is a small data transmission(SDT), and wherein the measurement report comprises informationindicating the DVT associated with the SDT.
 22. The WTRU of claim 19,wherein the processor is further configured to: determine, based on theconfiguration information, one or more positioning configurations of theset of positioning configurations, wherein each of the one or morepositioning configurations is associated with a respective payload sizebeing less than the threshold, and wherein the positioning configurationis selected from the one or more positioning configurations and isassociated with the payload size being closest to the threshold.
 23. TheWTRU of claim 19, wherein the one or more positioning configurationssatisfy a positioning requirement, wherein the positioning requirementcomprises one or more quality of service (QoS) requirements forpositioning, and wherein the one or more QoS requirements comprise aminimum accuracy requirement and/or a latency requirement forpositioning.
 24. The WTRU of claim 19, wherein the processor is furtherconfigured to determine, based on the configuration information, thateach of the set of positioning configurations is 1) associated with arespective payload size being equal to or more than the threshold or 2)does not satisfy a positioning requirement, and the transmitter isfurther configured to send a connection request requesting a transitionfrom a low-power connectivity mode to a connected mode to performpositioning measurement and measurement reporting.
 25. The WTRU of claim19, wherein the transmitter is further configured to: send an indicationindicating a set of payload sizes, wherein each payload size of the setof payload sizes is associated with a respective positioningconfiguration of the set of positioning configurations; or send anindication indicating 1) the respective payload size associated with therespective positioning configuration of the set of positioningconfigurations or 2) the payload size associated with the selectedpositioning configuration.
 26. The method of claim 1, furthercomprising: determining, based on the configuration information, one ormore positioning configurations of the set of positioningconfigurations, wherein each of the one or more positioningconfigurations is associated with a respective payload size being lessthan the threshold.
 27. The method of claim 26, wherein the positioningconfiguration is selected from the one or more positioningconfigurations and is associated with the payload size being closest tothe threshold.
 28. The method of claim 26, wherein the one or morepositioning configurations satisfy a positioning requirement, whereinthe positioning requirement comprises one or more quality of service(QoS) requirements for positioning, and wherein the one or more QoSrequirements comprise a minimum accuracy requirement and/or a latencyrequirement for positioning.
 29. The method of claim 1, wherein thethreshold is a data volume threshold (DVT), and wherein the datatransmission is a small data transmission (SDT).
 30. The method of claim1, further comprising sending the data transmission including themeasurement report.
 31. The method of claim 26, further comprising:sending an indication indicating 1) the respective payload sizeassociated with a respective positioning configuration of the one ormore positioning configurations or 2) the payload size associated withthe selected positioning configuration.
 32. The method of claim 26,wherein the one or more positioning configurations are determined basedon a satisfaction of a minimum positioning accuracy threshold and amaximum measurement payload size threshold.